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

ob-f/OpenBot

Measured 14 November 2026, 22:42 UTC, at code version 952b2c4

CAI score 35out of 100 At risk Down 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: 49,099 lines of product code in 15 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 20

Findings by how serious they are

149 critical 774 serious 148 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 22:42 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.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

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.
1037of 1071 findings point to an exact file and line, so you can open each one in the code. The other 34 concern the repository as a whole, such as missing documentation.
73dimensions across 7 lenses, read from 49,099 lines of product code in 15 projects.
Chapters

Executive summary

ob-f/OpenBot is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no automated security scanning of the code, its secrets or its dependencies, and it has tests that check nothing. It scores 35 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.

Production Readiness, at 20, is the weakest lens and counts most in the score. The best first step is making the three tests that check nothing check their results, worth about 12 points. Making the tests check their results comes next, worth about 10 points. Raising Production Readiness to 62 would lift the score to about 47.

Sixty-five known security holes in the packages the code depends on can be used by attackers. Thirty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and nine secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. The two pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The 14 images with no text description need a text description.

The product code is 49,099 lines, about €42,000 to rebuild.

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 20 · counts for 46%Accessibility 37 · counts for 25%Code Health 39 · counts for 14%Security and Compliance 70 · counts for 8%Architecture 72 · counts for 4%Maturity 78 · counts for 2%Performance 100 · counts for 1%

If Production Readiness rose from 20 to 62, the lowest score rated Strong, the score would rise from 35 to about 47.

Code composition: what the lines of code are
Product code 98%Tests 2%
New since the last survey: 193 findings

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

  • Cyclomatic Complexity · app.applyLive (cyclomatic 24) firmware/web/app.js
  • Cyclomatic Complexity · app.renderRobot (cyclomatic 17) firmware/web/app.js
  • Cognitive Complexity · applyLive (cognitive 28) firmware/web/app.js
  • Cognitive Complexity · build_site.body_info (cognitive 27) firmware/scripts/build_site.py
  • Cognitive Complexity · build_site.site (cognitive 17) firmware/scripts/build_site.py
  • Cognitive Complexity · renderRobot (cognitive 16) firmware/web/app.js
  • God Classes · FileTooLong: web/app.js firmware/web/app.js
  • Code Duplication · Near-duplicate member pair (36 shared lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (18 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift
  • Code Duplication · Edited copy of a member (23 corresponding lines) robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift
  • Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) policy/openbot/models.py
  • Code Duplication · Edited copy of a member (79 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (37 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift
  • Code Duplication · Edited copy of a member (34 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift
  • Code Duplication · Edited copy of a member (35 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift
  • Code Duplication · Edited copy of a member (29 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (36 corresponding lines) robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift
  • Code Duplication · Edited copy of a member (48 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift
  • Code Duplication · Edited copy of a member (30 corresponding lines) robot/ios/OpenBot/OpenBot/Utils/Common.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (39 corresponding lines) policy/openbot/dataloader.py
  • Code Duplication · Edited copy of a member (16 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/Data/GameController.swift
  • Code Duplication · Edited copy of a member (28 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java
  • Code Duplication · Edited copy of a member (35 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java
  • Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift
  • Code Duplication · Edited copy of a member (19 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java
  • Code Duplication · Edited copy of a member (13 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (35 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Edited copy of a member (13 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift
  • Code Duplication · Edited copy of a member (36 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java
  • Code Duplication · Edited copy of a member (24 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (25 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java
  • Code Duplication · Edited copy of a member (18 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift
  • Code Duplication · Edited copy of a member (23 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/env/ImageUtils.java
  • Code Duplication · Edited copy of a member (21 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java
  • Code Duplication · Edited copy of a member (23 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java
  • Code Duplication · Edited copy of a member (14 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift
  • Code Duplication · Edited copy of a member (15 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Edited copy of a member (29 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java
  • Code Duplication · Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift
  • Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift
  • Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift
  • Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift
  • Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java
  • Code Duplication · Edited copy of a member (17 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift
  • Code Duplication · Edited copy of a member (20 corresponding lines) robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift
  • Code Duplication · Edited copy of a member (27 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java
  • Code Duplication · Edited copy of a member (18 corresponding lines) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift
  • Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift
  • Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Edited copy of a member (21 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java
  • Code Duplication · Edited copy of a member (17 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java
  • Code Duplication · Edited copy of a member (18 corresponding lines) robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/GameView/GameViewController.swift
  • Code Duplication · Edited copy of a member (21 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/tflite/Model.swift
  • Code Duplication · Edited copy of a member (17 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java
  • Code Duplication · Edited copy of a member (14 corresponding lines) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift
  • Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift
  • Code Duplication · Edited copies of one member (7 members, 7+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Bluetooth/BluetoothTable.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift
  • Code Duplication · Edited copy of a member (21 corresponding lines) robot/ios/OpenBot/OpenBot/Utils/BlueDress/CVMetalTexture+.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/profile/ProfileFragment.java
  • Code Duplication · Edited copy of a member (6 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) robot/ios/OpenBot/OpenBot/Data/DataLogger.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift
  • Code Duplication · Edited copies of one member (4 members, 10+ corresponding lines) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ImageFrame.java
  • Code Duplication · Edited copy of a member (6 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Utils/Common.swift

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

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

  • Code Duplication · Near-duplicate member family (3 members, 9 shared lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Near-duplicate member pair (24 shared lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift
  • Code Duplication · Edited copy of a member (18 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift
  • Code Duplication · Edited copy of a member (23 corresponding lines) robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift
  • Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) policy/openbot/models.py
  • Code Duplication · Duplicated block (13 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift
  • Code Duplication · Duplicated block (9 lines × 2) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift
  • Code Duplication · Duplicated block (8 lines × 2) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift
  • Code Duplication · Duplicated block (8 lines × 2) robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift
  • Code Duplication · Duplicated block (7 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift
  • Code Duplication · Duplicated block (7 lines × 2) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift
  • Code Duplication · Duplicated block (6 lines × 2) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift
  • Code Duplication · Duplicated block (5 lines × 2) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift
  • Code Duplication · Duplicated block (6 lines × 2) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift
  • Code Duplication · Duplicated block (42 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java
  • Code Duplication · Duplicated block (5 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java
  • Code Duplication · Duplicated block (16 lines × 2) policy/openbot/train.py
  • Code Duplication · Duplicated block (6–8 lines × 3) policy/openbot/train.py
  • Churn × Complexity Hotspots · Hotspot: robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java
  • Churn × Complexity Hotspots · Hotspot: robot/android/app/src/main/java/org/openbot/app/robot/main/SettingsFragment.java robot/android/app/src/main/java/org/openbot/app/robot/main/SettingsFragment.java
  • Churn × Complexity Hotspots · Hotspot: controller/flutter/lib/screens/component/onScreenIcon.dart controller/flutter/lib/screens/component/onScreenIcon.dart
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Static Analysis (SAST) · High: REDACTED REDACTED
  • Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
  • Supply-chain Provenance & Signing · REDACTED REDACTED
  • Test Coverage · No test reaches this file controller/web-server/client/keyboardHandlers/buttons.js
  • Test Coverage · No test reaches this file open-code/src/components/blockly/index.js
  • Test Coverage · No test reaches this file open-code/src/components/blockly/blocks/field_toggle.js
  • Test Coverage · No test reaches this file open-code/src/components/homeComponents/carousel/carousel.js
  • Test Coverage · No test reaches this file open-code/src/components/subscription/subscriptionModel.js
  • Test Coverage · No test reaches this file controller/node-js/client/buttons.js
  • Test Coverage · No test reaches this file open-code/src/context/context.js
  • Test Coverage · No test reaches this file open-code/src/components/router/router.js
  • Test Coverage · No test reaches this file open-code/src/components/homeComponents/cookies/cookies.js
  • Test Coverage · No test reaches this file controller/node-js/client/bot-message-handler.js
  • Test Coverage · No test reaches this file controller/node-js/server/connection-manager.js
  • Test Coverage · No test reaches this file controller/web-server/client/firebase/authentication.js
  • Test Coverage · No test reaches this file open-code/src/components/blockly/blocks/generalBlocks.js
  • Test Coverage · No test reaches this file open-code/src/components/blockly/fields/BlocklyReactField.jsx
  • Test Coverage · No test reaches this file open-code/src/components/qrcode/qrcode.js
  • Test Coverage · No test reaches this file REDACTED
  • Test Coverage · No test reaches this file open-code/src/apis/models.js
  • Test Coverage · No test reaches this file open-code/src/pages/playground/index.js
  • Test Coverage · No test reaches this file open-code/src/components/blockly/fields/DateField.jsx
  • Test Coverage · No test reaches this file controller/node-js/server/dns.js
  • Test Coverage · No test reaches this file controller/node-js/server/shutdown-service.js
  • Test Coverage · No test reaches this file controller/node-js/server/browser-connection.js
  • Test Coverage · No test reaches this file controller/node-js/client/index.js
  • Test Coverage · No test reaches this file controller/node-js/server/index.js
  • Test Coverage · No test reaches this file open-code/src/components/fonts/blackText.js
  • Test Coverage · No test reaches this file open-code/src/pages/home/index.js
  • Test Coverage · No test reaches this file open-code/src/components/buttonComponent/blueButtonComponent.js
  • Test Coverage · No test reaches this file policy/frontend/src/index.tsx
  • Test Coverage · No test reaches this file policy/frontend/src/setupProxy.js
  • Test Coverage · No test reaches this file open-code/src/components/fonts/blueText.js
  • Test Coverage · No test reaches this file open-code/src/components/fonts/whiteText.js
  • Test Coverage · No test reaches this file controller/node-js/client/error-display.js
  • Test Coverage · No test reaches this file controller/web-server/client/utils/error-display.js
  • Test Coverage · No test reaches this file open-code/src/components/loader/loaderComponent.js
  • Test Coverage · No test reaches this file open-code/src/index.js
  • Test Coverage · No test reaches this file policy/frontend/src/reportWebVitals.js
  • Exception handling · Swallowed exception (empty catch) open-code/src/services/workspace.js
  • Exception handling · Swallowed exception (empty catch) open-code/src/services/workspace.js
  • A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €42,000 · Estimate
Cost to rebuild€14,000 to €71,000, for 235 to 746 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 35. 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: 49,099 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 3 No assertions finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift, OpenBotUITestsLaunchTests.swift.
Raises the score by about 12 points · Low effort · Test Quality
2
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift.
Raises the score by about 10 points · Low effort · Test Quality
3
Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift.
Raises the score by about 10 points · Low effort · Test Quality

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 €42,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 20 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 3 No assertions finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 12 points for low effort, because it clears the 3 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 7% to 16% on every change. The history of the code shows how much it changes: about 257,657 lines over the last 90 days, which is about 1,044,942 lines a year. At that pace, the extra work comes to an estimated 186.8 to 1120.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch OpenBot OpenBot android android android:app android:app android:comlib android:comlib android:app->android:comlib controller-js controller-js open-code open-code openbot_controller openbot_controller openbot_frontend (Python) openbot_frontend (Python) openbot_frontend (npm) openbot_frontend (npm) server (controller/node-js/server) server) server (controller/web-server/server) server) web-server web-server

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.

96 modules, with 80 dependencies between them. One loop runs through 11 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 56 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 controller.node-js2 controller.node-js.client3 controller.node-js.server4 controller.python5 controller.python.common6 controller.python.keyboard-click7 controller.python.keyboard-pygame8 controller.web-server9 controller.web-server.client.firebase10 open-code.src.components.blockly.fields.BlocklyReactField11 org.openbot.app.robot.model12 org.openbot.app.robot.pointGoalNavigation.rendering13 org.openbot.app.robot.server14 policy.frontend.src.utils.useDatasets15 policy.frontend.src.utils.useProgress16 policy.openbot.train17 open-code.src.components.blockly.fields.DateField18 org.openbot.app.robot.tflite19 policy.frontend.src.pages20 policy.frontend.src.utils21 policy.frontend.src.utils.useModels22 policy.openbot23 org.openbot.app.robot.customview24 org.openbot.app.robot.tracking25 org.openbot.app.robot.utils26 org.openbot.app.robot.main27 org.openbot.app.robot.common28 org.openbot.app.robot.modelManagement29 org.openbot.app.robot.googleServices30 org.openbot.app.robot.pointGoalNavigation31 org.openbot.app.robot.projects32 org.openbot.app.robot.env33 org.openbot.app.robot.logging34 org.openbot.app.robot.profile35 org.openbot.app.robot.robot36 org.openbot.app.robot.vehicle37 org.openbot.app.robot38 org.openbot.app.robot.autopilot39 org.openbot.app.robot.objectNav40 org.openbot.app.robot.original
1 controller.node-js
2 controller.node-js.client
3 controller.node-js.server
4 controller.python
5 controller.python.common
6 controller.python.keyboard-click
7 controller.python.keyboard-pygame
8 controller.web-server
9 controller.web-server.client.firebase
10 open-code.src.components.blockly.fields.BlocklyReactField
11 org.openbot.app.robot.model
12 org.openbot.app.robot.pointGoalNavigation.rendering
13 org.openbot.app.robot.server
14 policy.frontend.src.utils.useDatasets
15 policy.frontend.src.utils.useProgress
16 policy.openbot.train
17 open-code.src.components.blockly.fields.DateField1
18 org.openbot.app.robot.tflite12
19 policy.frontend.src.pages21
20 policy.frontend.src.utils1
21 policy.frontend.src.utils.useModels1
22 policy.openbot3
23 org.openbot.app.robot.customview2
24 org.openbot.app.robot.tracking121
25 org.openbot.app.robot.utils11
26 org.openbot.app.robot.main624
27 org.openbot.app.robot.common1211131
28 org.openbot.app.robot.modelManagement5221
29 org.openbot.app.robot.googleServices1141
30 org.openbot.app.robot.pointGoalNavigation3111
31 org.openbot.app.robot.projects51421641
32 org.openbot.app.robot.env511
33 org.openbot.app.robot.logging131113
34 org.openbot.app.robot.profile111
35 org.openbot.app.robot.robot321
36 org.openbot.app.robot.vehicle133
37 org.openbot.app.robot1
38 org.openbot.app.robot.autopilot31311
39 org.openbot.app.robot.objectNav31411
40 org.openbot.app.robot.original2631492
Uses a module listed above itPart of a loopThe module itself
1 controller.node-js2 controller.node-js.client3 controller.node-js.server4 controller.python5 controller.python.common6 controller.python.keyboard-click7 controller.python.keyboard-pygame8 controller.web-server9 controller.web-server.client.firebase10 open-code.src.components.blockly.fields.BlocklyReactField11 org.openbot.app.robot.model12 org.openbot.app.robot.pointGoalNavigation.rendering13 org.openbot.app.robot.server14 policy.frontend.src.utils.useDatasets15 policy.frontend.src.utils.useProgress16 policy.openbot.train17 open-code.src.components.blockly.fields.DateField18 org.openbot.app.robot.tflite19 policy.frontend.src.pages20 policy.frontend.src.utils21 policy.frontend.src.utils.useModels22 policy.openbot23 org.openbot.app.robot.customview24 org.openbot.app.robot.tracking25 org.openbot.app.robot.utils26 org.openbot.app.robot.main27 org.openbot.app.robot.common28 org.openbot.app.robot.modelManagement29 org.openbot.app.robot.googleServices30 org.openbot.app.robot.pointGoalNavigation31 org.openbot.app.robot.projects32 org.openbot.app.robot.env33 org.openbot.app.robot.logging34 org.openbot.app.robot.profile35 org.openbot.app.robot.robot36 org.openbot.app.robot.vehicle37 org.openbot.app.robot38 org.openbot.app.robot.autopilot39 org.openbot.app.robot.objectNav40 org.openbot.app.robot.originalcontroller.node-js1controller.node-js.client2controller.node-js.server3controller.python4controller.python.common5controller.python.keyboard-click6controller.python.keyboard-pygame7controller.web-server8controller.web-server.client.firebase9open-code.src.components.blockly.fields.BlocklyReactField10org.openbot.app.robot.model11org.openbot.app.robot.pointGoalNavigation.rendering12org.openbot.app.robot.server13policy.frontend.src.utils.useDatasets14policy.frontend.src.utils.useProgress15policy.openbot.train16open-code.src.components.blockly.fields.DateField17org.openbot.app.robot.tflite18policy.frontend.src.pages19policy.frontend.src.utils20policy.frontend.src.utils.useModels21policy.openbot22org.openbot.app.robot.customview23org.openbot.app.robot.tracking24org.openbot.app.robot.utils25org.openbot.app.robot.main26org.openbot.app.robot.common27org.openbot.app.robot.modelManagement28org.openbot.app.robot.googleServices29org.openbot.app.robot.pointGoalNavigation30org.openbot.app.robot.projects31org.openbot.app.robot.env32org.openbot.app.robot.logging33org.openbot.app.robot.profile34org.openbot.app.robot.robot35org.openbot.app.robot.vehicle36org.openbot.app.robot37org.openbot.app.robot.autopilot38org.openbot.app.robot.objectNav39org.openbot.app.robot.original4011221113212111624121113152211141311151421641511131113111321133131311314112631492+56 more modules (most-connected shown)

At a glance — Code Health · 39% · Weak · gated by R1, R10, X5 ·

At a glance — Architecture · 72% · Adequate · gated by D6, R9 ·

At a glance — Maturity · 78% · Strong ·

At a glance — Readiness · 20% · Weak · gated by D10, R4, R8, P3, P7 ·

At a glance — Security · 70% · Adequate · gated by D29, D36 ·

At a glance — Accessibility · 37% · Weak · gated by AC1, AC4 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures112High / Critical
A05:2025 — Injection67High / Critical
A01:2025 — Broken Access Control2Medium

Roadmap

Top priorities: Resolve the 3 No assertions finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift, OpenBotUITestsLaunchTests.swift; Resolve the 2 Assertions commented out finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift; Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift.

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

Do thisHelpsEffortDimension
Resolve the 3 No assertions finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift, OpenBotUITestsLaunchTests.swift.+11.8 ptsLowTest Quality
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift.+9.8 ptsLowTest Quality
Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift.+9.8 ptsLowTest Quality
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+3.5 ptsMediumSecurity & performance tooling
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+3.5 ptsMediumDependency Hygiene
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+2.4 ptsMediumKeyboard semantics
Add tests that import the unreached modules (directly or through their public entry).+1.8 ptsMediumTest Coverage
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).+1.6 ptsMediumOutbound HTTP resilience

File quality

Per-file score 0–10 — a quality signature. Of 152 files carrying findings, judged against the Preview bar: 6% slop · 35% mixed · 59% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.4SlopStatic Analysis (SAST): High: REDACTED
REDACTED1.9SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.3SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
REDACTED3.0MixedStatic Analysis (SAST): High: REDACTED
REDACTED3.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED3.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED3.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED3.7MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedDependency Vulnerabilities: Critical CVE: REDACTED
robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift5.5MixedCyclomatic Complexity: runRobot.display (cyclomatic 19)
robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift5.5MixedCognitive Complexity: FreeRoamController.viewDidLoad (cognitive 18)
robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift5.5MixedCognitive Complexity: expandedAutoPilot.init (cognitive 17)
robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift5.5MixedGod Classes: TooManyMethods: PointGoalFragment

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

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

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

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

Could not be resolved — 19

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
D1D2D3D4D5D6D10D13D14D15D16D17D19D20D21D24D26D28D29D30D32D34D35D36D43D44AC1AC2AC3AC4AC5AC6AX10AX3AX4AX6AX8AX9M1M2M3M4P1P10P2P3P4P6P7PF3R1R10R11R2R3R4R6R7R8R9S1X16X18X19X2X21X25X26X28X29X3X30X5

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, 1037 of 1071 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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

Every finding is locatable in findings.md. Run 01a1dc3a-41c4-7bfb-a866-bdc794b2d944.

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: this repository's production source spans .ts, .tsx, .swift, .java, and our analyzer cannot run the .swift, .java test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 98.2% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • 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 5 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 13 test source file(s) (.py, .java, .js) that it cannot: it reads the test types the .swift frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .swift, .java, and no driveable swift suite surfaced for the .swift half on this scan; the jvm executor ran against the .java half and never executed — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `npm install --ignore-scripts` (no lockfile) in controller/node-js/ (10 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
  • D12 Dependency Hygiene — 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. Not scored — a Gradle build resolved 314 artifact(s) across its subprojects (112 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • 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.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (robot/android/comlib/build.gradle), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — 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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/BottomSheet.swift`, `robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift`, `robot/ios/OpenBot/OpenBot/Utils/GifLoader.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.
  • AX6 Interface segregation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Boot via AndroidApp (robot/android/app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: ailed with an exception. * What went wrong: Cannot locate tasks that match ':app:assembleDebug' as project 'app' not found in root project 'android'. * Try: > Run gradlew projects to get a list of a…; runtime evidence skipped (launch chosen because robot/android/app/build.gradle applies the Android application plugin and robot/android/gradlew builds 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.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Java, Kotlin, Python, Swift, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Python, Swift, c, cpp is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • R4 Test Coverage — 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. 36 further occurrence(s) are not listed individually; the score already reflects all 76.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X19 Unrestored process-global state — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X21 Side-effecting pattern guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X25 Inert configuration knob — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X26 Unsynchronised callback handoff — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
  • X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X30 Support guard that admits what it rejects — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

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.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • 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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity7.0 / 10Strong✓ 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 7.0 / 10 · rule-coverage 100% · ceiling Prevented

44 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RemoteKeyboard::processKey at 39. A further 5 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being remote_keyboard.RemoteKeyboard at 40 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: controller/web-server/client/keyboardHandlers/remote_keyboard.js (remote_keyboard.RemoteKeyboard at 40), controller/node-js/server/remote-keyboard.js (remote-keyboard.RemoteKeyboard at 29), open-code/src/components/drawer/drawer.js (drawer.RightDrawer at 26), open-code/src/components/navBar/header.js (header.RightSection at 17), robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java (BotFunctions.displaySensorData at 16). 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.

RemoteKeyboard::processKey (cyclomatic 39) · ×2controller/web-server/client/keyboardHandlers/remote_keyboard.js:19
ProfileOptionModal (cyclomatic 34)open-code/src/components/homeComponents/header/profileOptionModal.js:22
CommandHandler.handle_keys (cyclomatic 33)controller/python/keyboard-pygame.py:59
BlocklyComponent.BlocklyComponent (cyclomatic 32)open-code/src/components/blockly/BlocklyComponent.jsx:27
EditProfileModal (cyclomatic 28)open-code/src/components/homeComponents/header/editProfileModal.js:22

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

What to do

  1. Bring the 36 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RemoteKeyboard::processKey (cyclomatic 39), ProfileOptionModal (cyclomatic 34), CommandHandler.handle_keys (cyclomatic 33). — 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 36 together lifts Cyclomatic Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity6.1 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

96 method(s) exceeded the cognitive complexity threshold of 15; the worst was simpleInputComponent.SimpleInputComponent at 85.

RemoteKeyboard::processKey (cognitive 65) · ×2controller/web-server/client/keyboardHandlers/remote_keyboard.js:19
simpleInputComponent.SimpleInputComponent (cognitive 85)open-code/src/components/inputComponent/simpleInputComponent.js:14
CommandHandler.handle_keys (cognitive 80)controller/python/keyboard-pygame.py:59
associate_frames.match_frame_session (cognitive 50)policy/openbot/associate_frames.py:130
BottomBar::generateCode (cognitive 49)open-code/src/components/bottomBar/bottomBar.js:96

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

What to do

  1. Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with simpleInputComponent.SimpleInputComponent (cognitive 85), CommandHandler.handle_keys (cognitive 80), RemoteKeyboard::processKey (cognitive 65). — 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 Cognitive Complexity from 6.1 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D3 · God Classes6.2 / 10Adequate✓ Tool-verified

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

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

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

66 god class(es) detected.

TooManyMethods: Vehicle · ×22robot/android/app/src/main/java/org/openbot/app/robot/vehicle/Vehicle.java:18
ClassTooLong: jsEvaluator · ×16robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:13
FileTooLong: JsEvaluator/JsEvaluator.swift · ×10robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift
MethodTooLong: jsEvaluator.evaluateJavaScript · ×9robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:70
FunctionTooLong: bottomBar.BottomBar · ×9open-code/src/components/bottomBar/bottomBar.js:30

What to do

  1. Resolve the 22 TooManyMethods finding(s) in God Classes — start with Vehicle.java, FreeRoamController.swift, RobotInfoFrame.swift. — One of this dimension's main actionable groups (22 warning-level).
  2. Resolve the 16 ClassTooLong finding(s) in God Classes — start with JsEvaluator.swift, RunRobot.swift, WebRtcServer.java. — One of this dimension's main actionable groups (16 warning-level).
  3. Resolve the 10 FileTooLong finding(s) in God Classes — start with JsEvaluator.swift, WebRtcServer.java, RunRobot.swift. — One of this dimension's main actionable groups (10 warning-level).

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

D4 · Code Duplication4.5 / 10Weak✓ Tool-verified

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

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

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

166 duplicated block group(s) detected. 13.8 % of the production lines (6,766 of 49,099) are in a reported copy. A further 127 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (8 lines × 2) · ×15robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:248
Duplicated block (9 lines × 2) · ×13robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:510
Duplicated block (7 lines × 2) · ×12robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:274
Duplicated block (10 lines × 2) · ×11robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:426
Edited copy of a member (11 corresponding lines) · ×10robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:381

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

What to do

  1. Resolve the 15 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with AutopilotFragment.java (2), DataCollectionController.swift, JsEvaluator.swift. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 13 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with ExpandedAutoPilot.swift (5), AutopilotFragment.java (2), ExpandSetting.swift. — One of this dimension's main actionable groups (13 warning-level).
  3. Resolve the 12 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ExpandedAutoPilot.swift (3), ExpandSetting.swift (2), AutopilotFragment.java (2). — One of this dimension's main actionable groups (12 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

12 production modules (Gradle+npm+Python+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 4 of the 12 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)2.9 / 10Weak✓ 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 2.9 / 10 · rule-coverage 100% · ceiling Verified

43 of 73 classes have LCOM4 above 3.

Low cohesion: HomePageViewController (LCOM4 24) · ×43robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:38

What to do

  1. Resolve the 43 Low cohesion finding(s) in Cohesion (LCOM4) — start with Detector.swift (2), HomePageViewController.swift, JsEvaluator.swift. — One of this dimension's main actionable groups (43 warning-level).

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

D10 · Test Quality0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 5 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5 tests. Measured on the .swift suite only — at least 13 test source file(s) (.py, .java, .js) went unread, so its test quality is unmeasured and is not in these counts.

Assertions commented out: testExample · ×2robot/ios/OpenBot/OpenBotTests/OpenBotTests.swift:22
Test project verifies nothing: OpenBotTests · ×2robot/ios/OpenBot/OpenBotTests/OpenBotTests.swift:22
No assertions: testPerformanceExample · ×3robot/ios/OpenBot/OpenBotTests/OpenBotTests.swift:30

What to do

  1. Resolve the 3 No assertions finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift, OpenBotUITestsLaunchTests.swift. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Assertions commented out finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift. — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with OpenBotTests.swift, OpenBotUITests.swift. — One of this dimension's main actionable groups (2 issue-level).

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ 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 20 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 5 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 31 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 1 serious finding✓ 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: firmware/scripts/compile_all.py (4×18=72)

Hotspot: firmware/scripts/compile_all.pyfirmware/scripts/compile_all.py:293

What to do

  1. Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with compile_all.py. — One of this dimension's main actionable groups (1 warning-level).

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

D16 · Bus Factor9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java. Counted over 163 of the 311 production source files in this repository: 147 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.

Off-boarding risk: anonymized user #1

✓ On the Gold path — maintain.

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

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

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

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

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

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

TodoComment · ×8robot/ios/OpenBot/OpenBot/tflite/Detector.swift:225
FixmeCommentrobot/ios/OpenBot/OpenBot/Utils/GifLoader.swift:4

What to do

  1. Resolve the 8 TodoComment finding(s) in Explicit Debt — start with ArCore.java (2), SensorService.java (2), Detector.swift. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 1 FixmeComment finding(s) in Explicit Debt — start with GifLoader.swift. — One of this dimension's main actionable groups (1 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

2 of 2 documentation facets pass in full. 217 document(s) read across 7 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 foundrobot/ios/OpenBot/OpenBot.xcodeproj/project.pbxproj:1

What to do

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

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

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

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

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

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

3 naming inconsistencies among 101 declarations measured against a convention their peers follow.

`dummyProjectID` spells `ID` where 44 names in the project spell it `Id`robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:569
`leadingAnchorOFTable` spells `OF` where 35 names in the project spell it `Of`robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/BottomSheet.swift:14
`fileExistWithFileID` spells `ID` where 19 names in the project spell it `Id`open-code/src/services/googleDrive.js:110

What to do

  1. Resolve the 1 `dummyProjectID` spells `ID` where 44 names in the project spell it `Id` finding(s) in Naming Consistency — start with Authentication.swift. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `leadingAnchorOFTable` spells `OF` where 35 names in the project spell… finding(s) in Naming Consistency — start with BottomSheet.swift. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 `fileExistWithFileID` spells `ID` where 19 names in the project spell it… finding(s) in Naming Consistency — start with googleDrive.js. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value6.2 6.2 / 10Adequate✓ 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 6.2 / 10 · rule-coverage 100% · ceiling Documented

12 of 317 judged comments only repeat the code they sit on (3.8 %). 1 comment(s) in another language or script were not judged.

redundant comment · ×12controller/web-server/client/webRTC/webrtc.js:18
doc comments repeat the names · ×2open-code/src/components/bottomBar/bottomBar.js:502

What to do

  1. Resolve the 12 redundant comment finding(s) in Comment Value — start with bottomBar.js (3), googleDrive.js (3), webrtc.js. — One of this dimension's main actionable groups (12 recommendation-level).

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

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

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

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

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

3 of 15 build units (Gradle, Python, Xcode, checkout, 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)10.0 / 10Exemplary○ Nothing flagged

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

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

67 finding(s): 0 critical, 46 high, 18 medium, 3 low. 35 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 1 file(s) — `robot/android/gradlew` (line 72, line 173) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
  2. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  3. No action in Static Analysis (SAST) — all 35 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (35 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

95 finding(s): 17 critical, 48 high, 21 medium, 9 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 46 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (43), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (46 issue-level).
  2. Resolve the 16 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED. — One of this dimension's main actionable groups (16 issue-level).
  3. Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).

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

D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified

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

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

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

2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep could not parse 3 file(s) — `robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/BottomSheet.swift`, `robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift`, `robot/ios/OpenBot/OpenBot/Utils/GifLoader.swift` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.

REDACTED

What to do

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

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

D34 · Knowledge Freshness5.3 / 10Adequate✓ 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 5.3 / 10 · rule-coverage 100% · ceiling Documented

81 of 164 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift. Counted over 164 of the 311 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×9robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:1
Orphaned file · ×72robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:1
Further orphaned files (smaller)

What to do

  1. Resolve the 72 Orphaned file finding(s) in Knowledge Freshness — start with CVPixelBuffer.swift, PopupWindowView.swift, ArCore.java. — One of this dimension's main actionable groups (72 recommendation-level).
  2. Resolve the 9 Orphaned knowledge finding(s) in Knowledge Freshness — start with FreeRoamController.swift, ExpandSetting.swift, ObjectTrackingSettings.swift. — One of this dimension's main actionable groups (9 issue-level).
  3. Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.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
REDACTED

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

What to do

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

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

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 3 platform declaration(s) and 74 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.

AC1 · Text alternatives3.4 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×14) — controller/node-js/client/index.html:21, controller/node-js/client/index.html:40, controller/node-js/client/index.html:41, …

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels5.0 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — open-code/src/components/blockly/fields/DateField.jsx:30, policy/frontend/src/pages/SessionPage.tsx:133
  • This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×2) — policy/frontend/src/modals/DatasetModal.tsx:66, policy/frontend/src/modals/PublishModal.tsx:78

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure5.9 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — controller/node-js/client/index.html:2, controller/web-server/client/index.html:2
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. (×2) — open-code/public/index.html:2, policy/frontend/public/index.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×8) — controller/node-js/client/index.html:40, controller/node-js/client/index.html:41, controller/node-js/client/index.html:42, …

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety4.3 / 10Weak✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.Edit` sets color: white on background-color: #2e8fd6 — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — open-code/src/components/navBar/navbar.module.css:75
  • `.step::before` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — firmware/web/style.css:67
  • `.segmented button[aria-checked="true"]` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — firmware/web/style.css:91
  • `.chip[aria-checked="true"]` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — firmware/web/style.css:107
  • `.part.changed .part-text strong::after` sets color: #2b8ad8 on background-color: #1d3347 — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — firmware/web/style.css:126
  • `.primary` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — firmware/web/style.css:158
  • `.secondary` sets color: #2b8ad8 on background-color: #303030 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — firmware/web/style.css:160
  • `.ways button[aria-selected="true"]` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — firmware/web/style.css:173
  • `.planExpirationModel` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — open-code/src/components/subscription/subscriptionModel.module.css:2
  • `.profileOptionModalStyle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — open-code/src/components/navBar/navbar.module.css:20
  • `.Edit:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — open-code/src/components/navBar/navbar.module.css:86
  • `.editProfileModal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — open-code/src/components/navBar/navbar.module.css:184
  • `.logoutModalBox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — open-code/src/components/navBar/navbar.module.css:255
  • `.helpCenterModalBox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — open-code/src/components/navBar/navbar.module.css:308
  • `.inputSection` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — open-code/src/components/inputComponent/inputComponent.module.css:14
  • `.model` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — open-code/src/components/homeComponents/myProjects/newProject.module.css:122
  • `.sync` moves (`animation: rotation infinite 2s linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — open-code/src/components/navBar/navbar.module.css:54
  • `.spin` moves (`animation: spin 1ms 1`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — open-code/src/components/homeComponents/carousel/carousel.module.css:67

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition7.6 / 10Strong✓ 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.

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

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

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

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.

M1 · Documentation (README)9.2 / 10Exemplary✓ Tool-verified

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

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

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

P2 · Observability4.5 / 10Adequate✓ Tool-verified

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

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

  • Only 1/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `controller/flutter`, `controller/flutter/ios`, `controller/node-js/server`, `controller/python`, `robot/ios/OpenBot`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Add a health-check endpoint (a /health route on your Vapor/Hummingbird router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 14 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
  • `controller/node-js/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — controller/node-js/package.json:17

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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 Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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

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

  • `new OkHttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — robot/android/app/src/main/java/org/openbot/app/robot/env/PhoneController.java:139
  • `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — robot/android/app/src/main/java/org/openbot/app/robot/projects/DownloadFileTask.java:51, robot/android/app/src/main/java/org/openbot/app/robot/projects/ReadFileTask.java:30
  • `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — robot/linux/download_data.py:10

What to do

  • Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
  • Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ 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.

R1 · Type Safety2.5 / 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.

  • 27 typed · 82 plain JS — the untyped files are controller/node-js/client/bot-message-handler.js, controller/node-js/client/buttons.js, REDACTED, controller/node-js/client/error-display.js, controller/node-js/client/index.js, controller/node-js/client/keyboard.js (+76 more).
R10 · Code Duplication2.9 / 10Weak✓ Tool-verified

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

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

  • 8 duplicated blocks under open-code/src/components/ have copies in at least two of the sibling directories bottomBar, drawer, editor, homeComponents, navBar — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — open-code/src/components/bottomBar/modelUploadingComponent.js:177
  • 7 duplicated blocks under controller/ have copies in at least two of the sibling directories node-js, web-server — 6 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — controller/node-js/client/keyboard.js:23
  • open-code/src/components/blockly/generator/javascriptGenerator.js:53 · open-code/src/components/blockly/generator/pythonGenerator.js:24 — the two spans are one implementation copied and then locally edited — 1517 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — open-code/src/components/blockly/generator/javascriptGenerator.js:53
  • controller/node-js/client/keyboard.js:23 · controller/web-server/client/keyboardHandlers/keyboard.js:23 — the 2 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. — controller/node-js/client/keyboard.js:23
  • controller/node-js/server/remote-keyboard.js:25 · controller/web-server/client/keyboardHandlers/remote_keyboard.js:20 — the two spans are one implementation copied and then locally edited — 291 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — controller/node-js/server/remote-keyboard.js:25
  • controller/node-js/server/commands.js:11 · controller/web-server/client/keyboardHandlers/commands.js:11 — these 2 files are line-for-line copies of one another — 51 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — controller/node-js/server/commands.js:11
  • policy/frontend/src/modals/DatasetModal.tsx:20 · policy/frontend/src/modals/PublishModal.tsx:31 — the two spans are one implementation copied and then locally edited — 338 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — policy/frontend/src/modals/DatasetModal.tsx:20
  • open-code/src/utils/constants.js:23 · open-code/src/utils/constants.js:64 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — open-code/src/utils/constants.js:23
  • open-code/src/components/blockly/blocks/customblocks.js:164 · open-code/src/components/blockly/blocks/customblocks.js:203 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — open-code/src/components/blockly/blocks/customblocks.js:164
  • open-code/src/components/blockly/blocks/customblocks.js:359 · open-code/src/components/blockly/blocks/customblocks.js:393 · open-code/src/components/blockly/blocks/customblocks.js:427 · open-code/src/components/blockly/blocks/customblocks.js:461 — all 4 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — open-code/src/components/blockly/blocks/customblocks.js:359
  • controller/node-js/client/buttons.js:10 · controller/web-server/client/keyboardHandlers/buttons.js:10 — the two spans are one implementation copied and then locally edited — 209 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — controller/node-js/client/buttons.js:10
  • controller/node-js/client/bot-message-handler.js:14 · controller/web-server/client/keyboardHandlers/bot-message-handler.js:14 — the two spans are one implementation copied and then locally edited — 123 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — controller/node-js/client/bot-message-handler.js:14
  • controller/node-js/client/webrtc.js:24 · controller/web-server/client/webRTC/webrtc.js:19 — the two spans are one implementation copied and then locally edited — 130 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — controller/node-js/client/webrtc.js:24
  • open-code/src/services/googleDrive.js:358 · open-code/src/services/googleDrive.js:386 — 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. — open-code/src/services/googleDrive.js:358
  • open-code/src/components/bottomBar/modelUploadingComponent.js:177 · open-code/src/components/homeComponents/header/editProfileModal.js:176 — the 2 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. — open-code/src/components/bottomBar/modelUploadingComponent.js:177
  • open-code/src/components/blockly/blocks/generalBlocks.js:33 · open-code/src/components/blockly/toolbox/Toolbox.js:57 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — open-code/src/components/blockly/blocks/generalBlocks.js:33
  • open-code/src/components/inputComponent/simpleInputComponent.js:164 · open-code/src/components/inputComponent/simpleInputComponent.js:183 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — open-code/src/components/inputComponent/simpleInputComponent.js:164
  • open-code/src/components/blockly/toolbox/Toolbox.js:37 · open-code/src/components/blockly/toolbox/Toolbox.js:62 — 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. — open-code/src/components/blockly/toolbox/Toolbox.js:37
  • open-code/src/components/homeComponents/header/headerComponents.js:265 · open-code/src/components/navBar/header.js:75 — the two spans are one implementation copied and then locally edited — 81 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — open-code/src/components/homeComponents/header/headerComponents.js:265
  • open-code/src/components/bottomBar/modelUploadingComponent.js:42 · open-code/src/components/navBar/header.js:101 — the 2 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. — open-code/src/components/bottomBar/modelUploadingComponent.js:42
  • open-code/src/components/homeComponents/header/headerComponents.js:265 · open-code/src/components/homeComponents/header/profileOptionModal.js:58 — the two spans are one implementation copied and then locally edited — 80 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — open-code/src/components/homeComponents/header/headerComponents.js:265
  • open-code/src/components/bottomBar/bottomBar.js:403 · open-code/src/components/editor/codeEditor.js:32 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — open-code/src/components/bottomBar/bottomBar.js:403
  • open-code/src/apis/models.js:14 · open-code/src/apis/projects.js:18 — the 2 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. — open-code/src/apis/models.js:14
  • open-code/src/components/blockly/index.js:27 · open-code/src/components/blockly/index.js:39 · open-code/src/components/blockly/index.js:51 — all 3 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. — open-code/src/components/blockly/index.js:27
  • open-code/src/components/drawer/drawer.js:26 · open-code/src/components/editor/codeEditor.js:28 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — open-code/src/components/drawer/drawer.js:26
  • open-code/src/components/homeComponents/header/helpCenterModal.js:86 · open-code/src/components/homeComponents/header/helpCenterModal.js:102 — 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. — open-code/src/components/homeComponents/header/helpCenterModal.js:86
  • controller/web-server/client/index.js:109 · controller/web-server/client/index.js:201 — the two spans are one implementation copied and then locally edited — 64 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — controller/web-server/client/index.js:109
  • controller/web-server/client/index.js:173 · open-code/src/App.js:69 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — controller/web-server/client/index.js:173
  • firmware/web/app.js:548 · firmware/web/avr.js:54 — the 2 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. — firmware/web/app.js:548
  • policy/frontend/src/pages/HomePage.tsx:12 · policy/frontend/src/pages/HomePage.tsx:21 — 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. — policy/frontend/src/pages/HomePage.tsx:12
  • policy/frontend/src/pages/ModelsPage.tsx:79 · policy/frontend/src/pages/TrainPage.tsx:62 — 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. — policy/frontend/src/pages/ModelsPage.tsx:79
  • open-code/src/components/bottomBar/bottomBar.js:459 · open-code/src/components/bottomBar/bottomBar.js:469 · open-code/src/components/bottomBar/bottomBar.js:480 — all 3 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. — open-code/src/components/bottomBar/bottomBar.js:459
  • firmware/web/app.js:110 · firmware/web/app.js:118 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firmware/web/app.js:110
  • open-code/src/components/bottomBar/bottomBar.js:510 · open-code/src/components/bottomBar/bottomBar.js:515 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — open-code/src/components/bottomBar/bottomBar.js:510

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.
R11 · Import Boundaries8.9 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • controller/node-js/test/commands.test.js:12 reaches past another workspace package's public entry into its internals with a relative path (../server/commands.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — controller/node-js/test/commands.test.js:12

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity8.4 / 10Strong✓ 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.

  • processKey has cyclomatic complexity 39 and cognitive complexity 65; 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. — controller/web-server/client/keyboardHandlers/remote_keyboard.js:19
  • processKey has cyclomatic complexity 29 and cognitive complexity 35; 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. — controller/node-js/server/remote-keyboard.js:24
  • RightDrawer has cyclomatic complexity 26 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — open-code/src/components/drawer/drawer.js:22
  • ProfileOptionModal has cyclomatic complexity 26 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 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. — open-code/src/components/homeComponents/header/profileOptionModal.js:22
  • applyLive 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. — firmware/web/app.js:574
  • generateCode has cyclomatic complexity 21 and cognitive complexity 49; 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. — open-code/src/components/bottomBar/bottomBar.js:96
  • UploadCodeButton has cyclomatic complexity 18 and cognitive complexity 15; 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. — open-code/src/components/bottomBar/bottomBar.js:368
  • renderRobot has cyclomatic complexity 17 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 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. — firmware/web/app.js:386
  • Card has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — open-code/src/components/homeComponents/myProjects/card.js:30
  • EditProfileModal has cyclomatic complexity 15 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. — open-code/src/components/homeComponents/header/editProfileModal.js:22
  • handle has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — controller/web-server/client/keyboardHandlers/bot-message-handler.js:19
  • BottomBar has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — open-code/src/components/bottomBar/bottomBar.js:30
  • applyBlocker has cyclomatic complexity 12 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 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. — firmware/web/app.js:190
  • clickedButton has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — open-code/src/components/bottomBar/bottomBar.js:215
  • CreateNewProjectModal has cyclomatic complexity 11 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. — open-code/src/components/homeComponents/myProjects/newProjectButton.js:117
  • (anonymous) has cyclomatic complexity 11 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. — firmware/web/app.js:314
R3 · Large Files8.1 / 10Strong✓ 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.

  • open-code/src/components/blockly/blocks/customblocks.js has 953 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — open-code/src/components/blockly/blocks/customblocks.js:1
  • firmware/web/app.js has 706 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firmware/web/app.js:1
  • open-code/src/components/bottomBar/bottomBar.js has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — open-code/src/components/bottomBar/bottomBar.js:1
  • open-code/src/services/googleDrive.js has 465 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — open-code/src/services/googleDrive.js:1
  • open-code/src/services/workspace.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — open-code/src/services/workspace.js:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage2.6 / 10Weak✓ 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. (×40) — open-code/src/components/blockly/blocks/customblocks.js:1, firmware/web/app.js:1, open-code/src/components/bottomBar/bottomBar.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
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.7 / 10Exemplary✓ Tool-verified

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

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

  • Nothing imports this binding — it is safe to review for removal. (×6) — controller/web-server/client/firebase/authentication.js:21, open-code/src/components/blockly/blocks/generalBlocks.js:31, open-code/src/components/blockly/fields/DateField.jsx:39, …
  • 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. — controller/web-server/client/firebase/APIs.js:36

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 Hygiene0.0 / 10Critical✓ 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 but not declared in any reachable package.json — installs work only by hoisting accident. — policy/frontend/src/pages/ModelsPage.tsx:1
  • Declared in controller/node-js/server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×7)
  • Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×12)
  • Declared in policy/frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Only test files import it (first: policy/frontend/src/App.test.js:1) — move it to devDependencies. — policy/frontend/package.json:6

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports3.9 / 10Weak✓ 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.

  • open-code/src/App.js → open-code/src/components/router/router.js → open-code/src/App.js (one verified cycle inside a mutually-dependent group of 26 files) — open-code/src/App.js:2
  • open-code/src/apis/models.js → open-code/src/services/firebase.js → open-code/src/services/workspace.js → open-code/src/apis/models.js (one verified cycle inside a mutually-dependent group of 5 files) — open-code/src/apis/models.js:5

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `https://accounts.google.com/gsi/client` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — controller/web-server/client/index.html:14

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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/13 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.
  • `checkFileExistsInFolder` 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 })`. — open-code/src/services/googleDrive.js:132
  • `CreateFolder` 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 })`. — open-code/src/services/googleDrive.js:157
  • `getFolderId` 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 })`. — open-code/src/services/googleDrive.js:189
  • `getAllFilesFromGoogleDrive` 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 })`. — open-code/src/services/googleDrive.js:247
  • `getSelectedProjectFromGoogleDrive` 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 })`. — open-code/src/services/googleDrive.js:275
  • `deleteFileFromGoogleDrive` 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 })`. — open-code/src/services/googleDrive.js:298
  • `getShareableLink` 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 })`. — open-code/src/services/googleDrive.js:358
  • `getDownloadedLink` 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 })`. — open-code/src/services/googleDrive.js:386
  • `fileRename` 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 })`. — open-code/src/services/googleDrive.js:415
  • `makeFolderPublic` 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 })`. — open-code/src/services/googleDrive.js:447
  • `uploadTfliteFile` 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 })`. — open-code/src/services/googleDrive.js:474
  • `fetchBytes` 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 })`. — firmware/web/app.js:629
  • `start` 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 })`. — firmware/web/app.js:730

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.

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.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

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.5 / 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.

  • 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. (×12) — robot/android/app/src/main/java/org/openbot/app/robot/utils/ConnectionUtils.java:104, robot/android/app/src/main/java/org/openbot/app/robot/env/ConnectionMonitor.java:103, open-code/src/services/workspace.js:157, …
  • `catch (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. — REDACTED:287
  • `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — firmware/web/app.js:674
  • `catch (error)` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. — controller/web-server/client/websocket/connection.js:86
  • `except` 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. — controller/python/keyboard-click.py:82

What to do

  • Swallowed exception (empty catch)
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 types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

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

  • 0/24 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

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 Health39%Weak — gated by R1, R10, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture72%Adequate — gated by D6, R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity78%StrongSolid.
Readiness20%Weak — gated by D10, R4, R8, P3, P7Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security70%Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility37%Weak — gated by AC1, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 3 check(s) recorded observations but carry no score

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

  • SC1 Supply-chain hygiene — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

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

  • AX1 Captive dependencies — Not applicable: this repository's Dart imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. 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 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
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: ailed with an exception. * What went wrong: Cannot locate tasks that match ':app:assembleDebug' as project 'app' not found in root project 'android'. * Try: > Run gradlew projects to get a list of a…; runtime evidence skipped (launch chosen because robot/android/app/build.gradle applies the Android application plugin and robot/android/gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
  • D12 Dependency Hygiene — Not scored — a Gradle build resolved 314 artifact(s) across its subprojects (112 behind a shipped release, reported), but the currency signal was not established over the whole graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .dart, .ino, .java, .kt, .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • 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 — polyglot repository, one half has no runner
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 value object(s))
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
  • 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
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage data present for 2 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, 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.
  • R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • X1 Async correctness — X1 reached only 30% of this repository's production lines — swift (20,179 lines), java (17,794 lines), cpp (2,441 lines), c (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X12 Unreachable branch — X12 reached only 30% of this repository's production lines — swift (20,179 lines), java (17,794 lines), cpp (2,441 lines), c (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — X13 reached only 30% of this repository's production lines — swift (20,179 lines), java (17,794 lines), cpp (2,441 lines), c (1 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 41% of this repository's production lines — swift (20,179 lines), javascript (10,080 lines), cpp (2,441 lines), typescript (1,420 lines), c (1 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 — 149 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×46
  • 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
  • + 21 more in this group — see findings.md.
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
  • + 10 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC1 · Text alternatives · <img> without a text alternative · ×14
  • <img> without a text alternative controller/node-js/client/index.html:21 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/node-js/client/index.html:40 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/node-js/client/index.html:41 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/node-js/client/index.html:42 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/node-js/client/index.html:43 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/node-js/client/keyboard.js:21 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/node-js/client/keyboard.js:22 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/node-js/client/keyboard.js:23 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/node-js/client/keyboard.js:24 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/web-server/client/index.html:22 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/web-server/client/keyboardHandlers/keyboard.js:21 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/web-server/client/keyboardHandlers/keyboard.js:22 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/web-server/client/keyboardHandlers/keyboard.js:23 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative controller/web-server/client/keyboardHandlers/keyboard.js:24 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
D34 · Knowledge Freshness · Orphaned knowledge · ×9
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
  • Orphaned knowledge robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×8
  • Clickable element isn't keyboard-operable controller/node-js/client/index.html:40 — The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable controller/node-js/client/index.html:41 — The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable controller/node-js/client/index.html:42 — The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable controller/node-js/client/index.html:43 — The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable controller/web-server/client/index.html:46 — The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable controller/web-server/client/index.html:47 — The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable controller/web-server/client/index.html:48 — The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable controller/web-server/client/index.html:49 — The repo's own CSS styles .button with `cursor: pointer`, so this <img> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · Assertions commented out · ×2
  • Assertions commented out: testExample robot/ios/OpenBot/OpenBotTests/OpenBotTests.swift:22 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
  • Assertions commented out: testExample robot/ios/OpenBot/OpenBotUITests/OpenBotUITests.swift:26 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: OpenBotTests robot/ios/OpenBot/OpenBotTests/OpenBotTests.swift:22 — No conventional assertion call was detected in 2 of 2 tests in `OpenBotTests` — the project as a whole, not one method. 1 of them has its assertions commented out, so this suite did verify conventionally and was switched off — it is not an approval/verifier harness.
  • Test project verifies nothing: OpenBotUITests robot/ios/OpenBot/OpenBotUITests/OpenBotUITests.swift:26 — No conventional assertion call was detected in 3 of 3 tests in `OpenBotUITests` — the project as a whole, not one method. 1 of them has its assertions commented out, so this suite did verify conventionally and was switched off — it is not an approval/verifier harness.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×2
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'date-fns' · ×1
  • Unlisted import 'date-fns' policy/frontend/src/pages/ModelsPage.tsx:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (2 files) · ×1
  • Import cycle (2 files) open-code/src/App.js:2 — open-code/src/App.js → open-code/src/components/router/router.js → open-code/src/App.js (one verified cycle inside a mutually-dependent group of 26 files)
R9 · Circular Imports · Import cycle (3 files) · ×1
  • Import cycle (3 files) open-code/src/apis/models.js:5 — open-code/src/apis/models.js → open-code/src/services/firebase.js → open-code/src/services/workspace.js → open-code/src/apis/models.js (one verified cycle inside a mutually-dependent group of 5 files)
Serious — 774 finding(s)
D6 · Cohesion (LCOM4) · Low cohesion · ×43
  • Low cohesion: HomePageViewController (LCOM4 24) robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:38 — HomePageViewController's methods fall into 24 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 24 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: runOpenBotThread (LCOM4 18) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:433 — runOpenBotThread's methods fall into 18 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: bluetoothDataController (LCOM4 13) robot/ios/OpenBot/OpenBot/Data/BluetoothDataController.swift:10 — bluetoothDataController's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: popupWindowView (LCOM4 11) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:11 — popupWindowView's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: WebRTCClient (LCOM4 11) robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:18 — WebRTCClient's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: expandedAutoPilot (LCOM4 10) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:9 — expandedAutoPilot'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: expandSetting (LCOM4 10) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:10 — expandSetting'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: FreeRoamController (LCOM4 10) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:11 — FreeRoamController'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: ModelManagementTable (LCOM4 10) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:10 — ModelManagementTable'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: ObjectTrackingSettings (LCOM4 10) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:10 — ObjectTrackingSettings'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: PointGoalFragment (LCOM4 9) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:11 — PointGoalFragment'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: CameraController (LCOM4 8) robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:9 — CameraController's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Detector (LCOM4 8) robot/ios/OpenBot/OpenBot/tflite/Detector.swift:10 — Detector's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: BottomSheet (LCOM4 8) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/BottomSheet.swift:9 — BottomSheet's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: scannerFragment (LCOM4 8) robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:12 — scannerFragment's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: WebRTCDelegates (LCOM4 8) robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCDelegates.swift:13 — WebRTCDelegates's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DetectorFloatYoloV4 (LCOM4 7) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:8 — DetectorFloatYoloV4's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: DataCollectionController (LCOM4 7) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:12 — DataCollectionController's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: AppDelegate (LCOM4 6) robot/ios/OpenBot/OpenBot/AppDelegate.swift:9 — AppDelegate'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: SceneDelegate (LCOM4 6) robot/ios/OpenBot/OpenBot/SceneDelegate.swift:8 — SceneDelegate'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: DetectorFloatYoloV5 (LCOM4 6) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:8 — DetectorFloatYoloV5'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: Model (LCOM4 6) robot/ios/OpenBot/OpenBot/tflite/Model.swift:67 — Model'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: BluetoothTable (LCOM4 6) robot/ios/OpenBot/OpenBot/Controllers/Bluetooth/BluetoothTable.swift:8 — BluetoothTable'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: GameViewController (LCOM4 6) robot/ios/OpenBot/OpenBot/Controllers/GameView/GameViewController.swift:8 — GameViewController'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: projectFragment (LCOM4 6) robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:11 — projectFragment'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.
  • + 18 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×40
  • No test reaches this file open-code/src/components/blockly/blocks/customblocks.js: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 firmware/web/app.js: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 open-code/src/components/bottomBar/bottomBar.js: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 open-code/src/services/googleDrive.js: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 open-code/src/services/workspace.js: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 open-code/src/utils/constants.js: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 open-code/src/components/blockly/generator/javascriptGenerator.js: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 open-code/src/components/homeComponents/header/headerComponents.js: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 open-code/src/components/blockly/generator/pythonGenerator.js: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 open-code/src/components/navBar/header.js: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 open-code/src/components/blockly/BlocklyComponent.jsx: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 open-code/src/components/homeComponents/header/editProfileModal.js: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 open-code/src/components/bottomBar/modelUploadingComponent.js: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 controller/web-server/client/index.js: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 open-code/src/components/homeComponents/myProjects/card.js: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 open-code/src/components/homeComponents/myProjects/newProjectButton.js: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 open-code/src/components/inputComponent/simpleInputComponent.js: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 open-code/src/App.js: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 open-code/src/components/homeComponents/header/profileOptionModal.js: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 controller/web-server/client/keyboardHandlers/keyboard.js: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 firmware/web/avr.js: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 open-code/src/components/blockly/toolbox/Toolbox.js: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 open-code/src/components/drawer/drawer.js: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 controller/node-js/server/remote-keyboard.js: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 controller/web-server/server/server.js: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.
  • + 15 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×22
  • TooManyMethods: Vehicle robot/android/app/src/main/java/org/openbot/app/robot/vehicle/Vehicle.java:18 — TooManyMethods — 87 methods. The bar is 30 methods; this is 57 over it, 2.90× 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: FreeRoamController robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:11 — TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.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: RobotInfoFrame robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:8 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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: BotFunctions robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:36 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× 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: expandSetting robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:10 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: WebRtcServer robot/android/app/src/main/java/org/openbot/app/robot/env/WebRtcServer.java:75 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: runRobot robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:12 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: runOpenBotThread robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:433 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: projectFragment robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:11 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× 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: PermissionUtils robot/android/app/src/main/java/org/openbot/app/robot/utils/PermissionUtils.java:27 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: ModelManagementTable robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:10 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ObjectTrackingSettings robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:10 — TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SharedPreferencesManager robot/android/app/src/main/java/org/openbot/app/robot/env/SharedPreferencesManager.java:14 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: expandedAutoPilot robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:9 — 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: SettingsFragment robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:12 — 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: ObjectNavFragment robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:51 — 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: AutopilotFragment robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:46 — 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.
  • TooManyMethods: ControlsFragment robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:46 — 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.
  • TooManyMethods: bluetoothDataController robot/ios/OpenBot/OpenBot/Data/BluetoothDataController.swift:10 — 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.
  • TooManyMethods: WebRTCClient robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:18 — 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.
  • TooManyMethods: HomePageViewController robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:38 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PointGoalFragment robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:11 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities · Medium CVE · ×21
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · ClassTooLong · ×16
  • ClassTooLong: jsEvaluator robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:13 — ClassTooLong — 658 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 258 over it, 1.65× 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: runRobot robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:12 — ClassTooLong — 621 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 221 over it, 1.55× 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: WebRtcServer robot/android/app/src/main/java/org/openbot/app/robot/env/WebRtcServer.java:75 — ClassTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 172 over it, 1.43× 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: FreeRoamController robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:11 — ClassTooLong — 556 significant lines (blank, comment-only and punctuation-only lines excluded), 64 methods. The bar is 400 significant lines; this is 156 over it, 1.39× 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: expandSetting robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:10 — ClassTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), 51 methods. The bar is 400 significant lines; this is 113 over it, 1.28× 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: BotFunctions robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:36 — ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 400 significant lines; this is 80 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: LoggerFragment robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:55 — ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 78 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ObjectTrackingSettings robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:10 — ClassTooLong — 476 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 76 over it, 1.19× 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: ObjectNavFragment robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:51 — ClassTooLong — 472 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 72 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: RobotInfoFrame robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:8 — ClassTooLong — 458 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 400 significant lines; this is 58 over it, 1.15× 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: BlocklyExecutingFragment robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:56 — ClassTooLong — 448 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 48 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ControlsFragment robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:46 — ClassTooLong — 416 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 16 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AutopilotFragment robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:46 — ClassTooLong — 413 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 13 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: expandedAutoPilot robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:9 — ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 12 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: projectFragment robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:11 — ClassTooLong — 408 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 400 significant lines; this is 8 over it, 1.02× 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: GoogleServices robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:56 — ClassTooLong — 402 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 2 over it, 1.01× 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 · Duplicated block (8 lines × 2) · ×15
  • Duplicated block (8 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:248 — robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:248-255 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:261-268 — 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 `robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:248` 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) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:864 — robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:864-871 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:883-890 — 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 `robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:864` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:63 — robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:63-70 | robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:122-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) robot/ios/OpenBot/OpenBot/tflite/Model.swift:179 — robot/ios/OpenBot/OpenBot/tflite/Model.swift:179-186 | robot/ios/OpenBot/OpenBot/tflite/Model.swift:197-204 — 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) robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:47 — robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:47-54 | robot/ios/OpenBot/OpenBot/server/NsdService.swift:54-61 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift` and `robot/ios/OpenBot/OpenBot/server/NsdService.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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 `robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) robot/ios/OpenBot/OpenBot/tflite/Network.swift:62 — robot/ios/OpenBot/OpenBot/tflite/Network.swift:62-69 | robot/ios/OpenBot/OpenBot/tflite/Network.swift:80-87 — 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 `robot/ios/OpenBot/OpenBot/tflite/Network.swift:62` 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) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:378 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:378-385 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:423-430 — 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) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:203 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:203-210 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:158-165 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 (8 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:45 — robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:45-52 | robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:155-162 — 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 `robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:45` 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 (8 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/env/RtspServer.java:57 — robot/android/app/src/main/java/org/openbot/app/robot/env/RtspServer.java:57-64 | robot/android/app/src/main/java/org/openbot/app/robot/env/WebRtcServer.java:129-136 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:366 — robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:366-373 | robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java:1115-1122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:181 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:181-188 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:189-196 — 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) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:518 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:518-525 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:591-598 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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 (8 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:485 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:485-492 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:559-566 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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 (8 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/vehicle/BluetoothManager.java:295 — robot/android/app/src/main/java/org/openbot/app/robot/vehicle/BluetoothManager.java:295-302 | robot/android/app/src/main/java/org/openbot/app/robot/vehicle/UsbConnection.java:171-178 — 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 (9 lines × 2) · ×13
  • Duplicated block (9 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:510 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:510-518 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:471-479 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:523 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:523-531 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:482-490 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:370 — robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:370-378 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:442-450 — 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 (9 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:185 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:185-193 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:201-209 — 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 `robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:185` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:168 — robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:168-176 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:207-215 — 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 `robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:168` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:323 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:323-331 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:754-762 — 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 `robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:323` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:323 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:323-331 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:273-281 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:323` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:67 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:67-75 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:73-81 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:237 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:237-245 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:147-155 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:237` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:456 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:456-464 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:544-552 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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. 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 (9 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:477 — robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:477-485 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:310-318 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:477` 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, `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:475` calls `elapsedRealtime` and `robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:309` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:290 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:290-298 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:365-373 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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) policy/openbot/models.py:97 — policy/openbot/models.py:97-105 | policy/openbot/models.py:177-185 — 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 `policy/openbot/models.py:97` 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.
X2 · Cancellation propagation · Async function without AbortSignal · ×13
  • Async function without AbortSignal: checkFileExistsInFolder open-code/src/services/googleDrive.js:132 — `checkFileExistsInFolder` 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 })`.
  • Async function without AbortSignal: CreateFolder open-code/src/services/googleDrive.js:157 — `CreateFolder` 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 })`.
  • Async function without AbortSignal: getFolderId open-code/src/services/googleDrive.js:189 — `getFolderId` 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 })`.
  • Async function without AbortSignal: getAllFilesFromGoogleDrive open-code/src/services/googleDrive.js:247 — `getAllFilesFromGoogleDrive` 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 })`.
  • Async function without AbortSignal: getSelectedProjectFromGoogleDrive open-code/src/services/googleDrive.js:275 — `getSelectedProjectFromGoogleDrive` 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 })`.
  • Async function without AbortSignal: deleteFileFromGoogleDrive open-code/src/services/googleDrive.js:298 — `deleteFileFromGoogleDrive` 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 })`.
  • Async function without AbortSignal: getShareableLink open-code/src/services/googleDrive.js:358 — `getShareableLink` 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 })`.
  • Async function without AbortSignal: getDownloadedLink open-code/src/services/googleDrive.js:386 — `getDownloadedLink` 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 })`.
  • Async function without AbortSignal: fileRename open-code/src/services/googleDrive.js:415 — `fileRename` 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 })`.
  • Async function without AbortSignal: makeFolderPublic open-code/src/services/googleDrive.js:447 — `makeFolderPublic` 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 })`.
  • Async function without AbortSignal: uploadTfliteFile open-code/src/services/googleDrive.js:474 — `uploadTfliteFile` 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 })`.
  • Async function without AbortSignal: fetchBytes firmware/web/app.js:629 — `fetchBytes` 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 })`.
  • Async function without AbortSignal: start firmware/web/app.js:730 — `start` 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 })`.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×12
  • Duplicated block (7 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:274 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:274-280 | robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:353-359 — 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 (7 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:457 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:457-463 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:576-582 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:693 — robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:693-699 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:707-713 — 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 `robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:693` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) robot/ios/OpenBot/OpenBot/tflite/Detector.swift:201 — robot/ios/OpenBot/OpenBot/tflite/Detector.swift:201-207 | robot/ios/OpenBot/OpenBot/tflite/Detector.swift:212-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (7 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:448 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:448-454 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:493-499 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:412 — robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:412-418 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:427-433 — 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 (7 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:609 — robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:609-615 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:524-530 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:157 — robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:157-163 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:196-202 — 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 (7 lines × 2) robot/ios/OpenBot/OpenBot/Data/GameController.swift:251 — robot/ios/OpenBot/OpenBot/Data/GameController.swift:251-257 | robot/ios/OpenBot/OpenBot/Data/GameController.swift:267-273 — 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 `robot/ios/OpenBot/OpenBot/Data/GameController.swift:251` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/env/GameController.java:149 — robot/android/app/src/main/java/org/openbot/app/robot/env/GameController.java:149-155 | robot/android/app/src/main/java/org/openbot/app/robot/env/GameController.java:174-180 — 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 (7 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:98 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:98-104 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:133-139 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:320 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:320-326 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:395-401 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×12
  • Swallowed exception (empty catch) robot/android/app/src/main/java/org/openbot/app/robot/utils/ConnectionUtils.java:104 — 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) robot/android/app/src/main/java/org/openbot/app/robot/env/ConnectionMonitor.java:103 — 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) open-code/src/services/workspace.js:157 — 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) open-code/src/services/workspace.js:182 — 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) firmware/web/app.js:164 — 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) firmware/web/app.js:212 — 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) firmware/web/app.js:221 — 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) firmware/web/app.js:517 — 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) firmware/web/app.js:552 — 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) firmware/web/app.js:665 — 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) firmware/web/avr.js:51 — 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) firmware/web/avr.js:58 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×11
  • Duplicated block (10 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:426 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:426-435 | robot/ios/OpenBot/OpenBot/Controllers/Modes/VehicleControl.swift:127-136 — 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 `robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:426` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:125 — robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:125-134 | robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCDelegates.swift:58-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.
  • Duplicated block (10 lines × 2) robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:78 — robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:78-87 | robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:106-115 — 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 `robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (10 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:334 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:334-343 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:284-293 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 (10 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:52 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:52-61 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:63-72 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 (10 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:170 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:170-179 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:188-197 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 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 (10 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:87 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:87-96 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/Navigation.java:87-96 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:87` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:279 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:279-288 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:322-331 — 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) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:303 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:303-312 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:355-364 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:303` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 2) policy/openbot/callbacks.py:9 — policy/openbot/callbacks.py:9-18 | policy/openbot/callbacks.py:22-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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (10 lines × 2) policy/openbot/callbacks.py:35 — policy/openbot/callbacks.py:35-44 | policy/openbot/callbacks.py:48-57 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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.
D3 · God Classes · FileTooLong · ×10
  • FileTooLong: JsEvaluator/JsEvaluator.swift robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift — FileTooLong — 662 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: jsEvaluator (13-1097). The bar is 500 significant lines; this is 162 over it, 1.32× 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: env/WebRtcServer.java robot/android/app/src/main/java/org/openbot/app/robot/env/WebRtcServer.java — FileTooLong — 628 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: WebRtcServer (75-944). The bar is 500 significant lines; this is 128 over it, 1.26× 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: runRobot/RunRobot.swift robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift — FileTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: runRobot (12-1057). The bar is 500 significant lines; this is 127 over it, 1.25× 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: web/app.js firmware/web/app.js — FileTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 67 over it, 1.13× 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: FreeRoam/FreeRoamController.swift robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift — FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: FreeRoamController (11-806). The bar is 500 significant lines; this is 65 over it, 1.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: openbot/train.py policy/openbot/train.py — FileTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 52 over it, 1.10× 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: logging/LoggerFragment.java robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java — FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: LoggerFragment (55-698). The bar is 500 significant lines; this is 30 over it, 1.06× 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: objectNav/ObjectNavFragment.java robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java — FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: ObjectNavFragment (51-695). The bar is 500 significant lines; this is 20 over it, 1.04× 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: DataCollection/ExpandSetting.swift robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift — FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: expandSetting (10-697). The bar is 500 significant lines; this is 16 over it, 1.03× 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: projects/BotFunctions.java robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java — FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: BotFunctions (36-699). The bar is 500 significant lines; this is 12 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×10
  • Edited copy of a member (11 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:381 — robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:381-391 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:700-711 — 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) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:467 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:467-477 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:476-489 — 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) robot/ios/OpenBot/OpenBot/Data/GameController.swift:247 — robot/ios/OpenBot/OpenBot/Data/GameController.swift:247-260 | robot/ios/OpenBot/OpenBot/Data/GameController.swift:266-276 — 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) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:302 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:302-312 | robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:283-294 — 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) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:236 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:236-247 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:400-410 — 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) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:321 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:321-331 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:271-281 — 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) robot/ios/OpenBot/OpenBot/tflite/Model.swift:176 — robot/ios/OpenBot/OpenBot/tflite/Model.swift:176-190 | robot/ios/OpenBot/OpenBot/tflite/Model.swift:196-206 — 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) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ImageFrame.java:58 — robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java:831-842 | robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ImageFrame.java:58-68 — 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) robot/ios/OpenBot/OpenBot/Data/Server/Connection.swift:27 — robot/ios/OpenBot/OpenBot/Data/Server/Connection.swift:27-39 | robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:16-26 — 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) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:382 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:382-393 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:811-821 — 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.
D3 · God Classes · MethodTooLong · ×9
  • MethodTooLong: jsEvaluator.evaluateJavaScript robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:70 — MethodTooLong — evaluateJavaScript runs 248 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 148 over it, 2.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: OnScreenIconState.build controller/flutter/lib/screens/component/onScreenIcon.dart:42 — MethodTooLong — build runs 166 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 66 over it, 1.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TiltingPhoneModeState.build controller/flutter/lib/screens/tiltingPhoneMode.dart:58 — MethodTooLong — build runs 140 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: SettingsFragment.onCreatePreferences robot/android/app/src/main/java/org/openbot/app/robot/main/SettingsFragment.java:85 — MethodTooLong — onCreatePreferences runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ObjectNavFragment.onViewCreated robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:106 — MethodTooLong — onViewCreated runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× 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: ControlsFragment.onViewCreated robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:75 — MethodTooLong — onViewCreated runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LoggerFragment.setupLoggerUi robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:107 — MethodTooLong — setupLoggerUi runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SensorService.onStartCommand robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:109 — MethodTooLong — onStartCommand runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SensorService.onSensorChanged robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:262 — MethodTooLong — onSensorChanged runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · FunctionTooLong · ×9
  • FunctionTooLong: bottomBar.BottomBar open-code/src/components/bottomBar/bottomBar.js:30 — FunctionTooLong — BottomBar runs 243 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× 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: modelUploadingComponent.ModelUploadingComponent open-code/src/components/bottomBar/modelUploadingComponent.js:21 — FunctionTooLong — ModelUploadingComponent runs 162 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: editProfileModal.EditProfileModal open-code/src/components/homeComponents/header/editProfileModal.js:22 — FunctionTooLong — EditProfileModal runs 161 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 61 over it, 1.61× 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: simpleInputComponent.SimpleInputComponent open-code/src/components/inputComponent/simpleInputComponent.js:14 — FunctionTooLong — SimpleInputComponent runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× 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: BlocklyComponent.BlocklyComponent open-code/src/components/blockly/BlocklyComponent.jsx:27 — FunctionTooLong — BlocklyComponent runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: Toolbox.Toolbox open-code/src/components/blockly/toolbox/Toolbox.js:15 — FunctionTooLong — Toolbox runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: card.Card open-code/src/components/homeComponents/myProjects/card.js:30 — FunctionTooLong — Card runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× 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: App.App open-code/src/App.js:17 — FunctionTooLong — App 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.
  • FunctionTooLong: bottomBar.UploadCodeButton open-code/src/components/bottomBar/bottomBar.js:368 — FunctionTooLong — UploadCodeButton runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×9
  • Duplicated block (12 lines × 2) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:158 — robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:158-169 | robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:182-193 — 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 `robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:158` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:38 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:38-49 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:47-58 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:89 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:89-100 | robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:569-580 — 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:537 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:537-548 | robot/ios/OpenBot/OpenBot/Utils/Common.swift:34-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:51 — robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:51-62 | robot/ios/OpenBot/OpenBot/tflite/Navigation.swift:38-49 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift` and `robot/ios/OpenBot/OpenBot/tflite/Navigation.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/env/ImageUtils.java:106 — robot/android/app/src/main/java/org/openbot/app/robot/env/ImageUtils.java:106-117 | robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:212-223 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/env/ImageUtils.java:137 — robot/android/app/src/main/java/org/openbot/app/robot/env/ImageUtils.java:137-148 | robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:175-186 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:123 — robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:123-134 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:686-697 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:123` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:169 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:169-180 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:247-258 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:169` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×9
  • Duplicated block (5 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:402 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:402-407 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:404-408 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:402` 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) robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:239 — robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:239-243 | robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:249-253 — 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 `robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:239` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:238` calls `move`, `CGPoint` and `robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:248` 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 (5 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:285 — robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:285-289 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:236-240 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:16 — robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:16-21 | robot/ios/OpenBot/OpenBot/server/NsdService.swift:14-18 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift` and `robot/ios/OpenBot/OpenBot/server/NsdService.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:160 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:160-164 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:163-167 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:160` 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) robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:59 — robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:59-63 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:59-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/profile/ProfileFragment.java:54 — robot/android/app/src/main/java/org/openbot/app/robot/profile/ProfileFragment.java:54-58 | robot/android/app/src/main/java/org/openbot/app/robot/projects/ProjectsFragment.java:79-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/InfoDialogFragment.java:41 — robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/InfoDialogFragment.java:41-45 | robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PermissionDialogFragment.java:35-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:105 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:105-109 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:188-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:105` 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.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×8
  • Focus outline removed in CSS without a :focus replacement open-code/src/components/subscription/subscriptionModel.module.css:2 — `.planExpirationModel` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement open-code/src/components/navBar/navbar.module.css:20 — `.profileOptionModalStyle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement open-code/src/components/navBar/navbar.module.css:86 — `.Edit:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement open-code/src/components/navBar/navbar.module.css:184 — `.editProfileModal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement open-code/src/components/navBar/navbar.module.css:255 — `.logoutModalBox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement open-code/src/components/navBar/navbar.module.css:308 — `.helpCenterModalBox` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement open-code/src/components/inputComponent/inputComponent.module.css:14 — `.inputSection` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement open-code/src/components/homeComponents/myProjects/newProject.module.css:122 — `.model` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
D17 · Explicit Debt · TodoComment · ×8
  • TodoComment robot/ios/OpenBot/OpenBot/tflite/Detector.swift:225 — // TODO: return ObjectTrackingFragment.MINIMUM_CONFIDENCE_TF_OD_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 robot/android/app/src/main/java/org/openbot/app/robot/server/ServerCommunication.java:125 — // TODO: Fix the commented code. — 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 robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ArCore.java:205 — // TODO: If needed, we could possibly implement some performance optimization 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 robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ArCore.java:217 — // TODO: We could use another data structure here to avoid additional copying later. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:484 — // TODO Auto-generated catch block — 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 robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:493 — // TODO Auto-generated catch block — 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 controller/flutter/lib/screens/tiltingPhoneMode.dart:51 — // TODO: implement didUpdateWidget — 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 controller/flutter/lib/screens/component/onScreenIcon.dart:33 — // TODO: implement didUpdateWidget — 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.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×8
  • Duplicated block (11 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:538 — robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:538-548 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:804-814 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:830 — robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:830-840 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:862-872 — 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 `robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:830` 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) robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:20 — robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:20-30 | robot/ios/OpenBot/OpenBot/tflite/Navigation.swift:21-31 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift` and `robot/ios/OpenBot/OpenBot/tflite/Navigation.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:152 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:152-162 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:208-218 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 (11 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:193 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:193-203 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:256-266 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:267` calls `setDynamicSpeed`, `getDynamicSpeed` and `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:205` 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 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:481 — robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:481-491 | robot/android/app/src/main/java/org/openbot/app/robot/original/DefaultActivity.java:204-214 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:481` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:343 — robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:343-353 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:640-650 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:343` 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, `robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:341` calls `showPermissionDialog` and `robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:639` 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 (11 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:225 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:225-235 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:290-300 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:303` calls `resetFpsUi` and `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:238` 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.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×7
  • Members sharing a duplicated core (4 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:315 — robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:315-322 | robot/ios/OpenBot/OpenBot/Controllers/Profile/EditProfileFragment.swift:375-382 | robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:233-240 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:431-442 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:475 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:475-483 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:635-643 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:679-687 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:299-307 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:527 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:527-545 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:560-578 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:604-622 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:222-240 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:547 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:547-570 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:580-603 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:624-647 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:242-267 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:572 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:572-590 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:605-623 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:649-667 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:269-287 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:285 — robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:285-340 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:347-394 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:396-448 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:538-593 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) policy/openbot/models.py:79 — policy/openbot/models.py:79-113 | policy/openbot/models.py:117-155 | policy/openbot/models.py:159-196 | policy/openbot/models.py:200-236 — 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 (10 corresponding lines) · ×7
  • Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:344 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:344-353 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:356-368 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:92 — robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:92-101 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:171-180 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:93 — robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:93-103 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:128-137 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:213 — robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:213-224 | robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCDelegates.swift:98-107 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:257 — robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:257-266 | robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:269-280 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Utils/Common.swift:108 — robot/ios/OpenBot/OpenBot/Utils/Common.swift:108-122 | robot/ios/OpenBot/OpenBot/Utils/Common.swift:143-152 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:307 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:307-316 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:735-746 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×6
  • Edited copy of a member (6 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:106 — robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:106-111 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:214-220 — 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) robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:312 — robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:312-317 | robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:221-232 — 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) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:224 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:224-229 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:263-268 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:136 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:136-141 | robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:149-154 — 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) robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:590 — robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:590-599 | robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java:656-661 — 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) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:369 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:369-374 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:795-802 — 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 (14 lines × 2) · ×6
  • Duplicated block (14 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:126 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:126-139 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:182-195 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:126` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:245 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:245-258 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:530-543 — 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 `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:245` 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 (14 lines × 2) robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:72 — robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:72-85 | robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:131-144 — 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 `robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:72` 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 (14 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:160 — robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:160-173 | robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java:384-397 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:160` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:495 — robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:495-508 | robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:675-688 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:495` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) policy/openbot/models.py:131 — policy/openbot/models.py:131-144 | policy/openbot/models.py:214-227 — 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 `policy/openbot/models.py: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `policy/openbot/models.py:145` calls `concatenate` and `policy/openbot/models.py:228` 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 lines × 2) · ×6
  • Duplicated block (6 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:363 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:363-368 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:408-413 — 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) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:23 — robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:23-28 | REDACTED:21-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:165 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:165-170 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:221-226 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:182 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:182-187 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:239-244 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:182` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:275 — robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:275-280 | robot/ios/OpenBot/OpenBot/Utils/extensions/UIViewExtension.swift:342-347 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) policy/openbot/utils.py:60 — policy/openbot/utils.py:60-65 | policy/openbot/utils.py:70-75 — 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 `policy/openbot/utils.py:60` 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.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.7 · ×5
  • Low contrast colour pair in CSS (3.7:1) firmware/web/style.css:67 — `.step::before` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.7:1) firmware/web/style.css:91 — `.segmented button[aria-checked="true"]` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.7:1) firmware/web/style.css:107 — `.chip[aria-checked="true"]` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.7:1) firmware/web/style.css:158 — `.primary` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.7:1) firmware/web/style.css:173 — `.ways button[aria-selected="true"]` sets color: #fff on background-color: #2b8ad8 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×5
  • Edited copy of a member (8 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:79 — robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:79-87 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:159-166 — 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) robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:127 — robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:127-139 | robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:180-187 — 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) robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:468 — robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:468-477 | robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:253-260 — 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) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:30 — robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:30-37 | REDACTED:28-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) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:570 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:570-578 | robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:606-613 — 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 (6 lines × 3) · ×5
  • Duplicated block (6 lines × 3) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:143 — robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:143-148 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:168-173 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:207-212 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (6 lines × 3) robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:167 — robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:167-172 | robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:196-201 | robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:223-228 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:602 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:602-607 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:645-650 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:689-694 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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 × 3) policy/openbot/models.py:108 — policy/openbot/models.py:108-113 | policy/openbot/models.py:149-155 | policy/openbot/models.py:188-196 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `policy/openbot/models.py:147` calls `Dropout` and `policy/openbot/models.py:106` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) policy/openbot/train.py:503 — policy/openbot/train.py:503-508 | policy/openbot/train.py:514-520 | policy/openbot/train.py:524-530 — 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 `policy/openbot/train.py:514` 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.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×5
  • JavaScript dependencies are not locked controller/node-js/package.json:17 — controller/node-js/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked controller/node-js/server/package.json:11 — controller/node-js/server/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked controller/web-server/package.json:21 — controller/web-server/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked controller/web-server/server/package.json:12 — controller/web-server/server/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked open-code/package.json:5 — open-code/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
AC3 · Page structure · Page without a main landmark · ×4
  • Page without a main landmark controller/node-js/client/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark controller/web-server/client/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark open-code/public/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark policy/frontend/public/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×4
  • Edited copy of a member (18 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:787 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:787-804 | robot/ios/OpenBot/OpenBot/Controllers/Modes/VehicleControl.swift:299-316 — 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) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:254 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:254-273 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:320-337 — 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) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:221 — robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:221-242 | robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:272-289 — 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) robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:77 — robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:77-94 | robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:104-129 — 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 (9 corresponding lines) · ×4
  • Edited copy of a member (9 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:234 — robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:234-243 | robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:245-253 — 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) robot/ios/OpenBot/OpenBot/Controllers/GameView/GameViewController.swift:174 — robot/ios/OpenBot/OpenBot/Controllers/GameView/GameViewController.swift:174-182 | robot/ios/OpenBot/OpenBot/Controllers/GameView/GameViewController.swift:190-198 — 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) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:449 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:449-457 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:460-468 — 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) robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:775 — robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:775-783 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:789-797 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×4
  • Edited copy of a member (16 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:443 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:443-468 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:492-507 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:153 — robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:153-169 | robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:178-193 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) robot/ios/OpenBot/OpenBot/Data/GameController.swift:118 — robot/ios/OpenBot/OpenBot/Data/GameController.swift:118-133 | robot/ios/OpenBot/OpenBot/Data/GameController.swift:142-157 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) controller/python/keyboard-click.py:111 — controller/python/keyboard-click.py:111-126 | controller/python/keyboard-pygame.py:319-338 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×4
  • Edited copy of a member (13 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:182 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:182-194 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:239-251 — 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.
  • Edited copy of a member (13 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:411 — robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:411-423 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:426-438 — 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.
  • Edited copy of a member (13 corresponding lines) robot/ios/OpenBot/OpenBot/Data/DataLogger.swift:85 — robot/ios/OpenBot/OpenBot/Data/DataLogger.swift:85-97 | robot/ios/OpenBot/OpenBot/Data/DataLogger.swift:266-278 — 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.
  • Edited copy of a member (13 corresponding lines) robot/ios/OpenBot/OpenBot/Utils/GifLoader.swift:32 — robot/ios/OpenBot/OpenBot/Utils/GifLoader.swift:32-44 | robot/ios/OpenBot/OpenBot/Utils/GifLoader.swift:50-63 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×4
  • Edited copy of a member (21 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:562 — robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:562-587 | robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java:633-653 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:359 — robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:359-383 | robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:385-405 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:335 — robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:335-357 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:635-655 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) robot/ios/OpenBot/OpenBot/Utils/BlueDress/CVMetalTexture+.swift:24 — robot/ios/OpenBot/OpenBot/Utils/BlueDress/CVMetalTexture+.swift:24-44 | robot/ios/OpenBot/OpenBot/Utils/BlueDress/CVMetalTexture+.swift:46-66 — 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 (5 corresponding lines) · ×4
  • Edited copy of a member (5 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:413 — robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:413-418 | robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java:1369-1373 — 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) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:257 — robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:257-263 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:706-710 — 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) robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:164 — robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:164-168 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:226-230 — 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) robot/android/app/src/main/java/org/openbot/app/robot/env/RtspServer.java:73 — robot/android/app/src/main/java/org/openbot/app/robot/env/RtspServer.java:73-79 | robot/android/app/src/main/java/org/openbot/app/robot/env/WebRtcServer.java:161-165 — 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 copy of a member (4 corresponding lines) · ×4
  • Edited copy of a member (4 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:87 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:87-90 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:92-95 — 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) robot/ios/OpenBot/OpenBot/Controllers/Bluetooth/BluetoothTable.swift:63 — robot/ios/OpenBot/OpenBot/Controllers/Bluetooth/BluetoothTable.swift:63-66 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:218-221 — 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) robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:276 — robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:276-279 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:97-100 — 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) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:403 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:403-406 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:342-345 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×4
  • Duplicated block (15 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:77 — robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:77-91 | robot/ios/OpenBot/OpenBot/tflite/Network.swift:92-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `robot/ios/OpenBot/OpenBot/Controllers/CameraController.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.
  • Duplicated block (15 lines × 2) robot/ios/OpenBot/OpenBot/Utils/Common.swift:232 — robot/ios/OpenBot/OpenBot/Utils/Common.swift:232-246 | robot/ios/OpenBot/OpenBot/Utils/Common.swift:270-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (15 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:787 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:787-801 | robot/ios/OpenBot/OpenBot/Controllers/Modes/VehicleControl.swift:299-313 — 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 `robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:787` 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) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:420 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:420-434 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:448-462 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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 `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:420` 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 (7 lines × 3) · ×4
  • Duplicated block (7 lines × 3) robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:118 — robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:118-124 | robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:366-373 | robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:395-401 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:118` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:393` calls `addAction`, `UIAlertAction`, `toggleSwitchButtons` and `robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:116` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:155 — robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:155-161 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:197-203 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:236-243 — 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 `robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:155` 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 × 3) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:157 — robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:157-163 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:217-223 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:275-281 — 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 `robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:157` 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 × 3) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:601 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:601-607 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:660-666 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:628-634 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×4
  • Duplicated block (8 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:593 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:593-600 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:626-633 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:670-677 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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. 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 (8 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:479 — robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:479-486 | robot/android/app/src/main/java/org/openbot/app/robot/original/DefaultActivity.java:202-209 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:312-319 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:479` 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, `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:475` calls `elapsedRealtime` and `robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:309` 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 (8 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:134 — robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:134-141 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:76-83 | robot/android/app/src/main/java/org/openbot/app/robot/robot/RobotInfoFragment.java:52-59 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 111 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:73` calls `setText`, `getString` and `robot/android/app/src/main/java/org/openbot/app/robot/robot/RobotInfoFragment.java:50` 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 (8 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:109 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:109-116 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:83-90 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:103-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×4
  • Outbound HTTP without resilience robot/android/app/src/main/java/org/openbot/app/robot/env/PhoneController.java:139 — `new OkHttpClient(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience robot/android/app/src/main/java/org/openbot/app/robot/projects/DownloadFileTask.java:51 — `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience robot/android/app/src/main/java/org/openbot/app/robot/projects/ReadFileTask.java:30 — `.openConnection(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
  • Outbound HTTP without resilience robot/linux/download_data.py:10 — `requests.get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×4
  • Swallowed exception (caught, then discarded) REDACTED:287 — `catch (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) firmware/web/app.js:674 — `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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) controller/web-server/client/websocket/connection.js:86 — `catch (error)` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
  • Swallowed exception (caught, then discarded) controller/python/keyboard-click.py:82 — `except` 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.
D10 · Test Quality · No assertions · ×3
  • No assertions: testPerformanceExample robot/ios/OpenBot/OpenBotTests/OpenBotTests.swift:30 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: testLaunchPerformance robot/ios/OpenBot/OpenBotUITests/OpenBotUITests.swift:34 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testLaunch robot/ios/OpenBot/OpenBotUITests/OpenBotUITestsLaunchTests.swift:21 — 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.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×3
  • Edited copy of a member (23 corresponding lines) robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:61 — robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:61-98 | robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:121-173 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/env/ImageUtils.java:103 — robot/android/app/src/main/java/org/openbot/app/robot/env/ImageUtils.java:103-125 | robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:209-231 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (23 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:365 — robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:365-387 | robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java:1114-1136 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (35 corresponding lines) · ×3
  • Edited copy of a member (35 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:502 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:502-536 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:539-573 — These two members are one piece of code written twice and then edited apart: 35 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 (35 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:182 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:182-217 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:231-265 — These two members are one piece of code written twice and then edited apart: 35 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 (35 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:189 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:189-223 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:252-288 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×3
  • Edited copy of a member (14 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:227 — robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:227-240 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:243-257 — 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) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:180 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:180-193 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:196-209 — 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) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:863 — robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:863-876 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:882-895 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 14+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:111 — robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:111-124 | robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:358-373 | robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:387-401 — 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.
  • Edited copies of one member (3 members, 14+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:232 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:232-245 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:109-122 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:142-155 — 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.
  • Edited copies of one member (3 members, 14+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:498 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:498-512 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:572-585 | robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java:999-1012 — 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 copy of a member (17 corresponding lines) · ×3
  • Edited copy of a member (17 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:117 — robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:117-134 | robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCDelegates.swift:51-67 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:41 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:41-59 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/Navigation.java:40-56 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:87 — robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:87-104 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:116-132 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×3
  • Duplicated block (16–17 lines × 2) robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:24 — robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:24-40 | robot/ios/OpenBot/OpenBot/server/NsdService.swift:21-36 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift` and `robot/ios/OpenBot/OpenBot/server/NsdService.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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 `robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift: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 (16–17 lines × 2) robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:91 — robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:91-107 | robot/ios/OpenBot/OpenBot/tflite/Navigation.swift:78-93 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift` and `robot/ios/OpenBot/OpenBot/tflite/Navigation.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 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 `robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:91` 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 (16–17 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:584 — robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:584-600 | robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:643-658 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:584` 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 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 × 3) · ×3
  • Duplicated block (12 lines × 3) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:414 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:414-425 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:370-381 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:415-426 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 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 (12 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:136 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:136-147 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:169-180 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:204-215 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:136` 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, `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:148` calls `get`, `contentEquals` and `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:216` 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 × 3) policy/openbot/models.py:83 — policy/openbot/models.py:83-94 | policy/openbot/models.py:121-132 | policy/openbot/models.py:163-174 — 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 `policy/openbot/models.py:83` 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.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×3
  • Duplicated block (10 lines × 2 locations) open-code/src/apis/models.js:14 — open-code/src/apis/models.js:14 · open-code/src/apis/projects.js:18 — the 2 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.
  • Duplicated block (10 lines × 2 locations) open-code/src/components/drawer/drawer.js:26 — open-code/src/components/drawer/drawer.js:26 · open-code/src/components/editor/codeEditor.js:28 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (10 lines × 2 locations) open-code/src/components/homeComponents/header/helpCenterModal.js:86 — open-code/src/components/homeComponents/header/helpCenterModal.js:86 · open-code/src/components/homeComponents/header/helpCenterModal.js:102 — 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.
AC2 · Forms & labels · <RadioGroup> field component without a label · ×2
  • <RadioGroup> field component without a label policy/frontend/src/modals/DatasetModal.tsx:66 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
  • <RadioGroup> field component without a label policy/frontend/src/modals/PublishModal.tsx:78 — This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.5 · ×2
  • Low contrast colour pair in CSS (3.5:1) open-code/src/components/navBar/navbar.module.css:75 — `.Edit` sets color: white on background-color: #2e8fd6 — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.5:1) firmware/web/style.css:126 — `.part.changed .part-text strong::after` sets color: #2b8ad8 on background-color: #1d3347 — 3.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×2
  • Animation without a prefers-reduced-motion guard open-code/src/components/navBar/navbar.module.css:54 — `.sync` moves (`animation: rotation infinite 2s linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard open-code/src/components/homeComponents/carousel/carousel.module.css:67 — `.spin` moves (`animation: spin 1ms 1`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D1 · Cyclomatic Complexity · RemoteKeyboard · ×2
  • RemoteKeyboard::processKey (cyclomatic 39) controller/web-server/client/keyboardHandlers/remote_keyboard.js:19 — RemoteKeyboard::processKey has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • RemoteKeyboard::processKey (cyclomatic 29) controller/node-js/server/remote-keyboard.js:24 — RemoteKeyboard::processKey has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · RemoteKeyboard · ×2
  • RemoteKeyboard::processKey (cognitive 65) controller/web-server/client/keyboardHandlers/remote_keyboard.js:19 — RemoteKeyboard::processKey has cognitive complexity 65 (threshold 15). Drivers by points: if/else 24 (62 pts), match/switch 2 (3 pts) (nesting depth added 39). 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.
  • RemoteKeyboard::processKey (cognitive 35) controller/node-js/server/remote-keyboard.js:24 — RemoteKeyboard::processKey has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (32 pts), match/switch 2 (3 pts) (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D32 · Data Compliance (PII/GDPR) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (6 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:250 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:250-290 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:394-432 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:714-743 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:413-453 | robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:35-100 | robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:148-210 — These 6 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 6 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 6 times.
  • Members sharing a duplicated core (6 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:102 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:102-133 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:143-182 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:185-214 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:121-182 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:192-261 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:264-323 — These 6 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 6 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 6 times.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×2
  • Edited copy of a member (29 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:288 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:288-318 | robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:346-374 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:418 — robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:418-451 | robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:453-481 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×2
  • Edited copy of a member (36 corresponding lines) robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:70 — robot/ios/OpenBot/OpenBot/tflite/Autopilot.swift:70-107 | robot/ios/OpenBot/OpenBot/tflite/Navigation.swift:58-93 — These two members are one piece of code written twice and then edited apart: 36 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 (36 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:432 — robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:432-469 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:663-698 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×2
  • Edited copy of a member (15 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:165 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:165-179 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:221-236 — 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) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:396 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:396-414 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:430-444 — 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 (7 corresponding lines) · ×2
  • Edited copy of a member (7 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:127 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:127-133 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:133-139 — 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) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:589 — robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:589-595 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:616-622 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 7+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:102 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:102-108 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:632-638 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:199-205 | robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:669-675 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 7+ corresponding lines) REDACTED:39 — REDACTED:39-48 | REDACTED:61-70 | REDACTED:74-80 | REDACTED:84-103 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×2
  • Edited copy of a member (3 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:170 — robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:170-172 | robot/ios/OpenBot/OpenBot/Controllers/HomePage/HomePageViewController.swift:106-110 — 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) robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:36 — robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:36-38 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:31-33 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×2
  • Duplicated block (20 lines × 3) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:100 — robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:100-119 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:253-272 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:299-318 — 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 `robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:100` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:106 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:106-125 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:149-168 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:189-208 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:106` 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, `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:128` calls `get`, `contentEquals` and `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:211` 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 (20 lines × 2) · ×2
  • Duplicated block (20 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:222 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:222-241 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:507-526 — 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 (20 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:428 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:428-447 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:940-959 — 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 (16 lines × 4) · ×2
  • Duplicated block (16 lines × 4) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:104 — robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:104-119 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:140-155 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:257-272 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:303-318 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (16 lines × 4) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:548 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:548-563 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:581-596 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:625-640 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:243-258 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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 `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:548` 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 `controlMode` to `Enums.ControlMode` in one and `ControlMode` 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 (14–15 lines × 2) · ×2
  • Duplicated block (14–15 lines × 2) robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:64 — robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:64-78 | robot/ios/OpenBot/OpenBot/server/NsdService.swift:75-88 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift` and `robot/ios/OpenBot/OpenBot/server/NsdService.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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 `robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:64` 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, `robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:61` calls `post` and `robot/ios/OpenBot/OpenBot/server/NsdService.swift:71` 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 (14–15 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/env/WebRtcServer.java:485 — robot/android/app/src/main/java/org/openbot/app/robot/env/WebRtcServer.java:485-498 | robot/android/app/src/main/java/org/openbot/app/robot/env/WebRtcServer.java:618-632 — 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 (26 lines × 2) · ×2
  • Duplicated block (26 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:75 — robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:75-100 | robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:185-210 — 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 `robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:75` 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 (26 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:184 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:184-209 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:233-258 — 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 (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:125 — robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:125-137 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:278-290 — 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 `robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:125` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:275 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:275-287 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:350-362 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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 `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:275` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×2
  • Duplicated block (14 lines × 3) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:335 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:335-348 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:520-533 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:557-570 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:334` calls `addGestureRecognizer` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:519` 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 (14 lines × 3) REDACTED:78 — REDACTED:78-91 | REDACTED:131-144 | REDACTED:169-182 — 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 `REDACTED:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:301 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:301-311 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:282-292 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:376-386 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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 (11 lines × 3) policy/openbot/models.py:79 — policy/openbot/models.py:79-89 | policy/openbot/models.py:117-127 | policy/openbot/models.py:200-210 — 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 `policy/openbot/models.py:79` 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.
R10 · Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) · ×2
  • Duplicated block with local edits (9 matched lines × 2 locations) controller/web-server/client/index.js:109 — controller/web-server/client/index.js:109 · controller/web-server/client/index.js:201 — the two spans are one implementation copied and then locally edited — 64 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
  • Duplicated block with local edits (9 matched lines × 2 locations) controller/web-server/client/index.js:173 — controller/web-server/client/index.js:173 · open-code/src/App.js:69 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×2
  • Duplicated block (9 lines × 2 locations) firmware/web/app.js:548 — firmware/web/app.js:548 · firmware/web/avr.js:54 — the 2 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.
  • Duplicated block (9 lines × 2 locations) policy/frontend/src/pages/HomePage.tsx:12 — policy/frontend/src/pages/HomePage.tsx:12 · policy/frontend/src/pages/HomePage.tsx:21 — 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.
R8 · Dependency Hygiene · Unused dependency '@testing-library/user-event' · ×2
  • Unused dependency '@testing-library/user-event' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Unused dependency '@testing-library/user-event' — Declared in policy/frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
AC2 · Forms & labels · <DatePicker> field component without a label · ×1
  • <DatePicker> field component without a label open-code/src/components/blockly/fields/DateField.jsx:30 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels · <Slider> field component without a label · ×1
  • <Slider> field component without a label policy/frontend/src/pages/SessionPage.tsx:133 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.6 · ×1
  • Low contrast colour pair in CSS (3.6:1) firmware/web/style.css:160 — `.secondary` sets color: #2b8ad8 on background-color: #303030 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · ProfileOptionModal (cyclomatic 34) · ×1
  • ProfileOptionModal (cyclomatic 34) open-code/src/components/homeComponents/header/profileOptionModal.js:22 — ProfileOptionModal has cyclomatic complexity 34 (threshold 15). Of this number, 26 points are the body's own statements and 8 belong to 13 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · CommandHandler.handle_keys (cyclomatic 33) · ×1
  • CommandHandler.handle_keys (cyclomatic 33) controller/python/keyboard-pygame.py:59 — CommandHandler.handle_keys has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · BlocklyComponent.BlocklyComponent (cyclomatic 32) · ×1
  • BlocklyComponent.BlocklyComponent (cyclomatic 32) open-code/src/components/blockly/BlocklyComponent.jsx:27 — BlocklyComponent.BlocklyComponent has cyclomatic complexity 32 (threshold 15). Most of this is not in the body itself: 3 of the 32 points are its own statements and the rest belongs to 9 function items inside it that branch (handlingBlocks, checkQRCode, a function literal at line 132, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · EditProfileModal (cyclomatic 28) · ×1
  • EditProfileModal (cyclomatic 28) open-code/src/components/homeComponents/header/editProfileModal.js:22 — EditProfileModal has cyclomatic complexity 28 (threshold 15). Of this number, 15 points are the body's own statements and 13 belong to 19 function items inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · associate_frames.match_frame_session (cyclomatic 27) · ×1
  • associate_frames.match_frame_session (cyclomatic 27) policy/openbot/associate_frames.py:130 — associate_frames.match_frame_session has cyclomatic complexity 27 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D1 · Cyclomatic Complexity · RightDrawer (cyclomatic 26) · ×1
  • RightDrawer (cyclomatic 26) open-code/src/components/drawer/drawer.js:22 — RightDrawer has cyclomatic complexity 26 (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 · SensorService.onStartCommand (cyclomatic 24) · ×1
  • SensorService.onStartCommand (cyclomatic 24) robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:109 — SensorService.onStartCommand 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 · app.applyLive (cyclomatic 24) · ×1
  • app.applyLive (cyclomatic 24) firmware/web/app.js:574 — app.applyLive has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 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 · simpleInputComponent.SimpleInputComponent (cyclomatic 24) · ×1
  • simpleInputComponent.SimpleInputComponent (cyclomatic 24) open-code/src/components/inputComponent/simpleInputComponent.js:14 — simpleInputComponent.SimpleInputComponent has cyclomatic complexity 24 (threshold 15). Of this number, 22 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 · Card (cyclomatic 24) · ×1
  • Card (cyclomatic 24) open-code/src/components/homeComponents/myProjects/card.js:30 — Card has cyclomatic complexity 24 (threshold 15). Of this number, 15 points are the body's own statements and 9 belong to 21 function items inside it that branch. 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 · ControlsFragment.onViewCreated (cyclomatic 23) · ×1
  • ControlsFragment.onViewCreated (cyclomatic 23) robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:75 — ControlsFragment.onViewCreated has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · OnScreenIconState.build (cyclomatic 23) · ×1
  • OnScreenIconState.build (cyclomatic 23) controller/flutter/lib/screens/component/onScreenIcon.dart:42 — OnScreenIconState.build has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · bottomBar.UploadCodeButton (cyclomatic 23) · ×1
  • bottomBar.UploadCodeButton (cyclomatic 23) open-code/src/components/bottomBar/bottomBar.js:368 — bottomBar.UploadCodeButton has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 3 function items inside it that branch. 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 · ControllerMappingFragment.processKeyEvent (cyclomatic 22) · ×1
  • ControllerMappingFragment.processKeyEvent (cyclomatic 22) robot/android/app/src/main/java/org/openbot/app/robot/controller/ControllerMappingFragment.java:95 — ControllerMappingFragment.processKeyEvent 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 · CVPixelBuffer.resized (cyclomatic 21) · ×1
  • CVPixelBuffer.resized (cyclomatic 21) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:17 — CVPixelBuffer.resized 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 · BottomBar · ×1
  • BottomBar::generateCode (cyclomatic 21) open-code/src/components/bottomBar/bottomBar.js:96 — BottomBar::generateCode 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 · SensorService.onDestroy (cyclomatic 20) · ×1
  • SensorService.onDestroy (cyclomatic 20) robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:442 — SensorService.onDestroy has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SettingsFragment.onCreatePreferences (cyclomatic 20) · ×1
  • SettingsFragment.onCreatePreferences (cyclomatic 20) robot/android/app/src/main/java/org/openbot/app/robot/main/SettingsFragment.java:85 — SettingsFragment.onCreatePreferences has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · GameController.processControllerKeyData (cyclomatic 19) · ×1
  • GameController.processControllerKeyData (cyclomatic 19) robot/ios/OpenBot/OpenBot/Data/GameController.swift:164 — GameController.processControllerKeyData 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 · runRobot.display (cyclomatic 19) · ×1
  • runRobot.display (cyclomatic 19) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:653 — runRobot.display has cyclomatic complexity 19 (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 · GameController.processButtonInput (cyclomatic 19) · ×1
  • GameController.processButtonInput (cyclomatic 19) robot/android/app/src/main/java/org/openbot/app/robot/env/GameController.java:51 — GameController.processButtonInput 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 · App (cyclomatic 19) · ×1
  • App (cyclomatic 19) open-code/src/App.js:17 — App has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 20 function items inside it that branch (getCookie, a function literal at line 92, a function literal at line 114, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · ServerWebrtcDelegate.didReceiveData (cyclomatic 18) · ×1
  • ServerWebrtcDelegate.didReceiveData (cyclomatic 18) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:35 — ServerWebrtcDelegate.didReceiveData 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. This shape REPEATS in the file: one other method here (ServerWebrtcDelegate.websocketDidReceiveMessage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · ServerWebrtcDelegate.websocketDidReceiveMessage (cyclomatic 18) · ×1
  • ServerWebrtcDelegate.websocketDidReceiveMessage (cyclomatic 18) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:148 — ServerWebrtcDelegate.websocketDidReceiveMessage 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. This shape REPEATS in the file: one other method here (ServerWebrtcDelegate.didReceiveData) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · SensorMessageHandler.handleMessage (cyclomatic 18) · ×1
  • SensorMessageHandler.handleMessage (cyclomatic 18) robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:401 — SensorMessageHandler.handleMessage 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 · compile_all.main (cyclomatic 18) · ×1
  • compile_all.main (cyclomatic 18) firmware/scripts/compile_all.py:293 — compile_all.main 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 · RightSection (cyclomatic 18) · ×1
  • RightSection (cyclomatic 18) open-code/src/components/navBar/header.js:206 — RightSection has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to 5 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · NsdService.start (cyclomatic 17) · ×1
  • NsdService.start (cyclomatic 17) robot/ios/OpenBot/OpenBot/server/NsdService.swift:21 — NsdService.start 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 · SettingsFragment.toggleSwitchButtons (cyclomatic 17) · ×1
  • SettingsFragment.toggleSwitchButtons (cyclomatic 17) robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:404 — SettingsFragment.toggleSwitchButtons has cyclomatic complexity 17 (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 · runRobot.runMultipleObjectTracking (cyclomatic 17) · ×1
  • runRobot.runMultipleObjectTracking (cyclomatic 17) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:859 — runRobot.runMultipleObjectTracking 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 · CVPixelBuffer.resizeAndCropTop (cyclomatic 17) · ×1
  • CVPixelBuffer.resizeAndCropTop (cyclomatic 17) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:176 — CVPixelBuffer.resizeAndCropTop 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 · ArCore.onDrawFrame (cyclomatic 17) · ×1
  • ArCore.onDrawFrame (cyclomatic 17) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ArCore.java:129 — ArCore.onDrawFrame 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 · app.renderRobot (cyclomatic 17) · ×1
  • app.renderRobot (cyclomatic 17) firmware/web/app.js:386 — app.renderRobot 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 · ModelUploadingComponent (cyclomatic 16) · ×1
  • ModelUploadingComponent (cyclomatic 16) open-code/src/components/bottomBar/modelUploadingComponent.js:21 — ModelUploadingComponent has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 17 function items inside it that branch. 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×1
  • Hotspot: firmware/scripts/compile_all.py firmware/scripts/compile_all.py:293 — firmware/scripts/compile_all.py changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in compile_all.main at line 293. 1 of those changes was a fix/bug commit, and the other 3 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-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:27:44 -08:00' --until='2026-11-13 17:27:44 -08:00' --full-history --no-merges -- firmware/scripts/compile_all.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D17 · Explicit Debt · FixmeComment · ×1
  • FixmeComment robot/ios/OpenBot/OpenBot/Utils/GifLoader.swift:4 — // FIXME: comparison operators with optionals were removed from the Swift Standard Library. — 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.
D2 · Cognitive Complexity · simpleInputComponent.SimpleInputComponent (cognitive 85) · ×1
  • simpleInputComponent.SimpleInputComponent (cognitive 85) open-code/src/components/inputComponent/simpleInputComponent.js:14 — simpleInputComponent.SimpleInputComponent has cognitive complexity 85 (threshold 15). Drivers by points: ternaries 20 (82 pts), if/else 1 (2 pts), boolean chains 1 (nesting depth added 63). Of this number, 78 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · CommandHandler.handle_keys (cognitive 80) · ×1
  • CommandHandler.handle_keys (cognitive 80) controller/python/keyboard-pygame.py:59 — CommandHandler.handle_keys has cognitive complexity 80 (threshold 15). Drivers by points: if/else 21 (77 pts), loops 2 (3 pts) (nesting depth added 57). To reduce it, split the body into named stages: move each independent 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 · associate_frames.match_frame_session (cognitive 50) · ×1
  • associate_frames.match_frame_session (cognitive 50) policy/openbot/associate_frames.py:130 — associate_frames.match_frame_session has cognitive complexity 50 (threshold 15). Drivers by points: if/else 20 (38 pts), boolean chains 6, loops 3 (6 pts) (nesting depth added 21). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D2 · Cognitive Complexity · BottomBar · ×1
  • BottomBar::generateCode (cognitive 49) open-code/src/components/bottomBar/bottomBar.js:96 — BottomBar::generateCode has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (32 pts), loops 3 (11 pts), error handling 1 (4 pts), boolean chains 2 (nesting depth added 28). 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 · BlocklyComponent.BlocklyComponent (cognitive 47) · ×1
  • BlocklyComponent.BlocklyComponent (cognitive 47) open-code/src/components/blockly/BlocklyComponent.jsx:27 — BlocklyComponent.BlocklyComponent has cognitive complexity 47 (threshold 15). Drivers by points: if/else 23 (33 pts), loops 3 (6 pts), boolean chains 4, ternaries 3, error handling 1 (nesting depth added 13). Most of this is not in the body itself: 2 of the 47 points are its own statements and the rest belongs to 9 function items inside it that branch (checkQRCode, handlingBlocks, a function literal at line 132, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · runRobot.runMultipleObjectTracking (cognitive 46) · ×1
  • runRobot.runMultipleObjectTracking (cognitive 46) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:859 — runRobot.runMultipleObjectTracking has cognitive complexity 46 (threshold 15). Drivers by points: if/else 14 (31 pts), loops 2 (11 pts), boolean chains 4 (nesting depth added 26). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · BlocklyExecutingFragment.followMultipleObject (cognitive 39) · ×1
  • BlocklyExecutingFragment.followMultipleObject (cognitive 39) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:347 — BlocklyExecutingFragment.followMultipleObject has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (35 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · SensorMessageHandler.handleMessage (cognitive 35) · ×1
  • SensorMessageHandler.handleMessage (cognitive 35) robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:401 — SensorMessageHandler.handleMessage has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (35 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 · EditProfileModal (cognitive 35) · ×1
  • EditProfileModal (cognitive 35) open-code/src/components/homeComponents/header/editProfileModal.js:22 — EditProfileModal has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 11, error handling 3 (8 pts), ternaries 2 (nesting depth added 10). Most of this is not in the body itself: 10 of the 35 points are its own statements and the rest belongs to 19 function items inside it that branch (handleSubmit, handleCompressFile, handleNameChange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · CVPixelBuffer.resized (cognitive 32) · ×1
  • CVPixelBuffer.resized (cognitive 32) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:17 — CVPixelBuffer.resized has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 5 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GoogleServices.accessDriveFiles (cognitive 32) · ×1
  • GoogleServices.accessDriveFiles (cognitive 32) robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:208 — GoogleServices.accessDriveFiles has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 5 (12 pts), error handling 1 (2 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 · runRobot.runDetection (cognitive 31) · ×1
  • runRobot.runDetection (cognitive 31) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:1010 — runRobot.runDetection has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 1 (3 pts), boolean chains 1 (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 · OnScreenIconState.build (cognitive 31) · ×1
  • OnScreenIconState.build (cognitive 31) controller/flutter/lib/screens/component/onScreenIcon.dart:42 — OnScreenIconState.build has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 14, loops 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · ProfileOptionModal (cognitive 31) · ×1
  • ProfileOptionModal (cognitive 31) open-code/src/components/homeComponents/header/profileOptionModal.js:22 — ProfileOptionModal has cognitive complexity 31 (threshold 15). Drivers by points: boolean chains 9, ternaries 8, if/else 6 (7 pts), error handling 2 (5 pts), other 2 (nesting depth added 4). Of this number, 16 points are the body's own statements and 15 belong to 13 function items inside it that branch. 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 · Authentication.googleSignInFunc (cognitive 29) · ×1
  • Authentication.googleSignInFunc (cognitive 29) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:43 — Authentication.googleSignInFunc has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 1 (3 pts), boolean chains 1, error handling 1 (nesting depth added 15). 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 · CameraController.initializeCamera (cognitive 29) · ×1
  • CameraController.initializeCamera (cognitive 29) robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:127 — CameraController.initializeCamera has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (24 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 16). 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 · ObjectNavFragment.processFrame (cognitive 29) · ×1
  • ObjectNavFragment.processFrame (cognitive 29) robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:447 — ObjectNavFragment.processFrame has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BlocklyExecutingFragment.onDetection (cognitive 29) · ×1
  • BlocklyExecutingFragment.onDetection (cognitive 29) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:396 — BlocklyExecutingFragment.onDetection has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 15). 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 · NsdService.start (cognitive 28) · ×1
  • NsdService.start (cognitive 28) robot/ios/OpenBot/OpenBot/server/NsdService.swift:21 — NsdService.start has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (20 pts), match/switch 3 (6 pts), loops 2 (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 · GoogleServices.createAndUploadJsonFile (cognitive 28) · ×1
  • GoogleServices.createAndUploadJsonFile (cognitive 28) robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:488 — GoogleServices.createAndUploadJsonFile has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · applyLive (cognitive 28) · ×1
  • applyLive (cognitive 28) firmware/web/app.js:574 — applyLive has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 8, ternaries 3 (4 pts) (nesting depth added 5). Of this number, 26 points are the body's own statements and 2 belong to 8 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 · App (cognitive 28) · ×1
  • App (cognitive 28) open-code/src/App.js:17 — App has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (17 pts), error handling 2 (4 pts), loops 2 (3 pts), ternaries 2 (3 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 20 function items inside it that branch (a function literal at line 114, getCookie, a function literal at line 92, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · CVPixelBuffer.resizeAndCropTop (cognitive 27) · ×1
  • CVPixelBuffer.resizeAndCropTop (cognitive 27) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:176 — CVPixelBuffer.resizeAndCropTop has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (25 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CommandHandler.handle_keys (cognitive 27) · ×1
  • CommandHandler.handle_keys (cognitive 27) controller/python/keyboard-click.py:34 — CommandHandler.handle_keys has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build_site.body_info (cognitive 27) · ×1
  • build_site.body_info (cognitive 27) firmware/scripts/build_site.py:138 — build_site.body_info has cognitive complexity 27 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 4 (9 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Authentication.getIdOfDriveFile (cognitive 26) · ×1
  • Authentication.getIdOfDriveFile (cognitive 26) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:348 — Authentication.getIdOfDriveFile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 15). 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 · ObjectTrackingFragment.captureOutput (cognitive 26) · ×1
  • ObjectTrackingFragment.captureOutput (cognitive 26) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:328 — ObjectTrackingFragment.captureOutput has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (20 pts), loops 2 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · compile_all.main (cognitive 26) · ×1
  • compile_all.main (cognitive 26) firmware/scripts/compile_all.py:293 — compile_all.main has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 6 (9 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileDownloader.loadFileAsync (cognitive 25) · ×1
  • FileDownloader.loadFileAsync (cognitive 25) robot/ios/OpenBot/OpenBot/Utils/FileDownloader.swift:46 — FileDownloader.loadFileAsync has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (25 pts) (nesting depth added 15). 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 · Network.init (cognitive 25) · ×1
  • Network.init (cognitive 25) robot/ios/OpenBot/OpenBot/tflite/Network.swift:39 — Network.init has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (6 pts), match/switch 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GoogleServices.getConfigFileContent (cognitive 25) · ×1
  • GoogleServices.getConfigFileContent (cognitive 25) robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:671 — GoogleServices.getConfigFileContent has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (9 pts), error handling 1 (2 pts), boolean chains 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 · DetectorYoloV5.getMultipleRecognitions (cognitive 25) · ×1
  • DetectorYoloV5.getMultipleRecognitions (cognitive 25) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:191 — DetectorYoloV5.getMultipleRecognitions has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 6 (10 pts), boolean chains 2 (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 · RightDrawer (cognitive 25) · ×1
  • RightDrawer (cognitive 25) open-code/src/components/drawer/drawer.js:22 — RightDrawer has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 23, boolean chains 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DetectorFloatYoloV5.getMultipleRecognitions (cognitive 24) · ×1
  • DetectorFloatYoloV5.getMultipleRecognitions (cognitive 24) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:166 — DetectorFloatYoloV5.getMultipleRecognitions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 6 (10 pts), boolean chains 2 (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 · SensorService.onStartCommand (cognitive 24) · ×1
  • SensorService.onStartCommand (cognitive 24) robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:109 — SensorService.onStartCommand has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14, boolean chains 10. 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 · SettingsFragment.onCreatePreferences (cognitive 24) · ×1
  • SettingsFragment.onCreatePreferences (cognitive 24) robot/android/app/src/main/java/org/openbot/app/robot/main/SettingsFragment.java:85 — SettingsFragment.onCreatePreferences has cognitive complexity 24 (threshold 15). Drivers by points: if/else 23, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · DetectorFloatYoloV5.getRecognitions (cognitive 23) · ×1
  • DetectorFloatYoloV5.getRecognitions (cognitive 23) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:105 — DetectorFloatYoloV5.getRecognitions has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 6 (10 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 · ArCore.onDrawFrame (cognitive 23) · ×1
  • ArCore.onDrawFrame (cognitive 23) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ArCore.java:129 — ArCore.onDrawFrame has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (18 pts), error handling 3 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DetectorYoloV5.getRecognitions (cognitive 23) · ×1
  • DetectorYoloV5.getRecognitions (cognitive 23) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:121 — DetectorYoloV5.getRecognitions has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 6 (10 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 · compile_all.check_defaults (cognitive 23) · ×1
  • compile_all.check_defaults (cognitive 23) firmware/scripts/compile_all.py:105 — compile_all.check_defaults has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 6 (9 pts), boolean chains 2, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ModelUploadingComponent (cognitive 23) · ×1
  • ModelUploadingComponent (cognitive 23) open-code/src/components/bottomBar/modelUploadingComponent.js:21 — ModelUploadingComponent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 6, error handling 2 (6 pts), ternaries 3, other 1 (nesting depth added 5). Most of this is not in the body itself: 7 of the 23 points are its own statements and the rest belongs to 17 function items inside it that branch (handleSubmit, handleTypeChange, handleTfliteNameChange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ServerCommunication.downloadFile (cognitive 22) · ×1
  • ServerCommunication.downloadFile (cognitive 22) robot/ios/OpenBot/OpenBot/server/ServerCommunication.swift:121 — ServerCommunication.downloadFile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (22 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DetectorFloatYoloV5.getAllRecognitions (cognitive 22) · ×1
  • DetectorFloatYoloV5.getAllRecognitions (cognitive 22) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:225 — DetectorFloatYoloV5.getAllRecognitions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 6 (10 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · scannerFragment.metadataOutput (cognitive 22) · ×1
  • scannerFragment.metadataOutput (cognitive 22) robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:134 — scannerFragment.metadataOutput has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Connection.receiveMessage (cognitive 22) · ×1
  • Connection.receiveMessage (cognitive 22) robot/ios/OpenBot/OpenBot/Data/Server/Connection.swift:74 — Connection.receiveMessage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConnectionMonitor.getIPAddress (cognitive 22) · ×1
  • ConnectionMonitor.getIPAddress (cognitive 22) robot/android/app/src/main/java/org/openbot/app/robot/env/ConnectionMonitor.java:81 — ConnectionMonitor.getIPAddress has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (13 pts), ternaries 1 (5 pts), loops 2 (3 pts), error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConnectionUtils.getIPAddress (cognitive 22) · ×1
  • ConnectionUtils.getIPAddress (cognitive 22) robot/android/app/src/main/java/org/openbot/app/robot/utils/ConnectionUtils.java:82 — ConnectionUtils.getIPAddress has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (13 pts), ternaries 1 (5 pts), loops 2 (3 pts), error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MultiBoxTracker.updateTarget (cognitive 22) · ×1
  • MultiBoxTracker.updateTarget (cognitive 22) robot/android/app/src/main/java/org/openbot/app/robot/tracking/MultiBoxTracker.java:154 — MultiBoxTracker.updateTarget has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 6 (11 pts) (nesting depth added 9). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D2 · Cognitive Complexity · dataloader.load_labels (cognitive 22) · ×1
  • dataloader.load_labels (cognitive 22) policy/openbot/dataloader.py:40 — dataloader.load_labels has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · bottomBar.BottomBar · ×1
  • bottomBar.BottomBar::handlingMultipleAIBlocks (cognitive 22) open-code/src/components/bottomBar/bottomBar.js:67 — bottomBar.BottomBar::handlingMultipleAIBlocks has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 1 (4 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · Card (cognitive 22) · ×1
  • Card (cognitive 22) open-code/src/components/homeComponents/myProjects/card.js:30 — Card has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10, boolean chains 5, if/else 4, error handling 2, other 1. Of this number, 14 points are the body's own statements and 8 belong to 21 function items inside it that branch. 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 · ControlsFragment.onViewCreated (cognitive 21) · ×1
  • ControlsFragment.onViewCreated (cognitive 21) robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:75 — ControlsFragment.onViewCreated has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · ControllerMappingFragment.processKeyEvent (cognitive 21) · ×1
  • ControllerMappingFragment.processKeyEvent (cognitive 21) robot/android/app/src/main/java/org/openbot/app/robot/controller/ControllerMappingFragment.java:95 — ControllerMappingFragment.processKeyEvent has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ControllerState.processMessageFromBot (cognitive 21) · ×1
  • ControllerState.processMessageFromBot (cognitive 21) controller/flutter/lib/screens/controller.dart:343 — ControllerState.processMessageFromBot has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (21 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GameController.processControllerKeyData (cognitive 20) · ×1
  • GameController.processControllerKeyData (cognitive 20) robot/ios/OpenBot/OpenBot/Data/GameController.swift:164 — GameController.processControllerKeyData has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · DataCollectionController.captureOutput (cognitive 20) · ×1
  • DataCollectionController.captureOutput (cognitive 20) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:209 — DataCollectionController.captureOutput has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (15 pts), match/switch 1 (3 pts), boolean chains 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 · projectFragment.loadProjects (cognitive 20) · ×1
  • projectFragment.loadProjects (cognitive 20) robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:384 — projectFragment.loadProjects has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 1 (3 pts) (nesting depth added 12). 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 · bottomBar.UploadCodeButton (cognitive 20) · ×1
  • bottomBar.UploadCodeButton (cognitive 20) open-code/src/components/bottomBar/bottomBar.js:368 — bottomBar.UploadCodeButton has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 14, boolean chains 4, if/else 2. Of this number, 15 points are the body's own statements and 5 belong to 3 function items inside it that branch. 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 · Browser.start (cognitive 19) · ×1
  • Browser.start (cognitive 19) robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:24 — Browser.start has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (6 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 · SensorService.onDestroy (cognitive 19) · ×1
  • SensorService.onDestroy (cognitive 19) robot/android/app/src/main/java/org/openbot/app/robot/logging/SensorService.java:442 — SensorService.onDestroy has cognitive complexity 19 (threshold 15). Drivers by points: if/else 19. 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 · DetectorYoloV5.getAllRecognition (cognitive 19) · ×1
  • DetectorYoloV5.getAllRecognition (cognitive 19) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:264 — DetectorYoloV5.getAllRecognition has cognitive complexity 19 (threshold 15). Drivers by points: loops 6 (10 pts), if/else 4 (9 pts) (nesting depth added 9). 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 · ControllerState.registerNewService (cognitive 19) · ×1
  • ControllerState.registerNewService (cognitive 19) controller/flutter/lib/screens/controller.dart:195 — ControllerState.registerNewService has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (3 pts), error handling 1 (2 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 · workspace.renameProject (cognitive 19) · ×1
  • workspace.renameProject (cognitive 19) open-code/src/services/workspace.js:263 — workspace.renameProject has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DetectorFloatYoloV4.getMultipleRecognitions (cognitive 18) · ×1
  • DetectorFloatYoloV4.getMultipleRecognitions (cognitive 18) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:163 — DetectorFloatYoloV4.getMultipleRecognitions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 4 (8 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FreeRoamController.viewDidLoad (cognitive 18) · ×1
  • FreeRoamController.viewDidLoad (cognitive 18) robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:36 — FreeRoamController.viewDidLoad has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LoggerFragment.processFrame (cognitive 18) · ×1
  • LoggerFragment.processFrame (cognitive 18) robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:655 — LoggerFragment.processFrame has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · 1.onReceive (cognitive 18) · ×1
  • 1.onReceive (cognitive 18) robot/android/app/src/main/java/org/openbot/app/robot/main/MainActivity.java:69 — 1.onReceive has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (16 pts), match/switch 1 (2 pts) (nesting depth added 12). 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 · Detector.multipleNMS (cognitive 18) · ×1
  • Detector.multipleNMS (cognitive 18) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Detector.java:318 — Detector.multipleNMS has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 5 (9 pts) (nesting depth added 10). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
D2 · Cognitive Complexity · Common.loadSelectedModels (cognitive 17) · ×1
  • Common.loadSelectedModels (cognitive 17) robot/ios/OpenBot/OpenBot/Utils/Common.swift:75 — Common.loadSelectedModels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DetectorFloatYoloV4.getRecognitions (cognitive 17) · ×1
  • DetectorFloatYoloV4.getRecognitions (cognitive 17) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:121 — DetectorFloatYoloV4.getRecognitions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expandedAutoPilot.init (cognitive 17) · ×1
  • expandedAutoPilot.init (cognitive 17) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:36 — expandedAutoPilot.init has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (3 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 · GameController.processJoystickInput (cognitive 17) · ×1
  • GameController.processJoystickInput (cognitive 17) robot/android/app/src/main/java/org/openbot/app/robot/env/GameController.java:126 — GameController.processJoystickInput has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · BlocklyExecutingFragment.startFollowObject (cognitive 17) · ×1
  • BlocklyExecutingFragment.startFollowObject (cognitive 17) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:285 — BlocklyExecutingFragment.startFollowObject has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BluetoothManager.addDeviceInfoDataAndUpdate (cognitive 17) · ×1
  • BluetoothManager.addDeviceInfoDataAndUpdate (cognitive 17) robot/android/app/src/main/java/org/openbot/app/robot/vehicle/BluetoothManager.java:166 — BluetoothManager.addDeviceInfoDataAndUpdate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build_site.site (cognitive 17) · ×1
  • build_site.site (cognitive 17) firmware/scripts/build_site.py:330 — build_site.site has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 4 (5 pts), boolean chains 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 · compile_all.mcu_combinations (cognitive 17) · ×1
  • compile_all.mcu_combinations (cognitive 17) firmware/scripts/compile_all.py:162 — compile_all.mcu_combinations has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · tfrecord.load_labels (cognitive 17) · ×1
  • tfrecord.load_labels (cognitive 17) policy/openbot/tfrecord.py:37 — tfrecord.load_labels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DetectorFloatYoloV4.getAllRecognitions (cognitive 16) · ×1
  • DetectorFloatYoloV4.getAllRecognitions (cognitive 16) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:205 — DetectorFloatYoloV4.getAllRecognitions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 4 (8 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 · ServerWebrtcDelegate.didReceiveData (cognitive 16) · ×1
  • ServerWebrtcDelegate.didReceiveData (cognitive 16) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:35 — ServerWebrtcDelegate.didReceiveData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 1 (2 pts), match/switch 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. This shape REPEATS in the file: one other method here (ServerWebrtcDelegate.websocketDidReceiveMessage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · ServerWebrtcDelegate.websocketDidReceiveMessage (cognitive 16) · ×1
  • ServerWebrtcDelegate.websocketDidReceiveMessage (cognitive 16) robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:148 — ServerWebrtcDelegate.websocketDidReceiveMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), error handling 1 (2 pts), match/switch 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. This shape REPEATS in the file: one other method here (ServerWebrtcDelegate.didReceiveData) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · runRobot.runObjectTracking (cognitive 16) · ×1
  • runRobot.runObjectTracking (cognitive 16) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:827 — runRobot.runObjectTracking has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BlocklyExecutingFragment.startMultipleAi (cognitive 16) · ×1
  • BlocklyExecutingFragment.startMultipleAi (cognitive 16) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:538 — BlocklyExecutingFragment.startMultipleAi has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 1 (2 pts), boolean chains 1 (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 · utils.compare_tf_tflite (cognitive 16) · ×1
  • utils.compare_tf_tflite (cognitive 16) policy/openbot/utils.py:141 — utils.compare_tf_tflite has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · renderRobot (cognitive 16) · ×1
  • renderRobot (cognitive 16) firmware/web/app.js:386 — renderRobot has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 5, ternaries 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
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
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (118 shared lines) · ×1
  • Near-duplicate member pair (118 shared lines) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:17 — robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:17-167 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:176-329 — These two members are variants of one another: 118 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (38 shared lines) · ×1
  • Near-duplicate member pair (38 shared lines) robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:24 — robot/ios/OpenBot/OpenBot/Data/Server/Browser.swift:24-78 | robot/ios/OpenBot/OpenBot/server/NsdService.swift:21-88 — These two members are variants of one another: 38 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (36 shared lines) · ×1
  • Near-duplicate member pair (36 shared lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:402 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:402-445 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:404-446 — These two members are variants of one another: 36 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (9 members, 50+ identical tokens) robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:154 — robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:154-180 | robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:183-208 | robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:210-233 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:121-161 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:163-203 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:205-243 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:105-163 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:166-223 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:225-281 — These 9 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 9 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 9 times.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (5 members, 50+ identical tokens) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:90 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:90-187 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:107-242 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:106-246 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:68-139 | robot/android/app/src/main/java/org/openbot/app/robot/robot/RobotInfoFragment.java:47-96 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (79 corresponding lines) · ×1
  • Edited copy of a member (79 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:36 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:36-114 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:41-135 — These two members are one piece of code written twice and then edited apart: 79 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 (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:140 — robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:140-176 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:179-215 — These two members are one piece of code written twice and then edited apart: 37 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 (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:323 — robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:323-362 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:754-787 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (48 corresponding lines) · ×1
  • Edited copy of a member (48 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:211 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:211-258 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:496-543 — 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 (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) robot/ios/OpenBot/OpenBot/Utils/Common.swift:231 — robot/ios/OpenBot/OpenBot/Utils/Common.swift:231-260 | robot/ios/OpenBot/OpenBot/Utils/Common.swift:269-301 — These two members are one piece of code written twice and then edited apart: 30 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 (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) policy/openbot/dataloader.py:41 — policy/openbot/dataloader.py:41-79 | policy/openbot/tfrecord.py:38-78 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:69 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:69-96 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/Navigation.java:69-96 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:369 — robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:369-388 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:391-408 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:441-462 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:132 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:132-154 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorDefault.java:202-220 — 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 (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:126 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:126-149 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:182-205 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:110 — robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java:110-134 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:672-697 — These two members are one piece of code written twice and then edited apart: 25 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, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:123 — robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:123-137 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:142-156 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:179-193 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 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, 26+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 26+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:340 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:340-365 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:503-540 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:317-352 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 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, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:252 — robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:252-266 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:269-280 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:349-360 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:363-377 — 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 copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:198 — robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:198-217 | robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:219-238 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:222 — robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:222-248 | robot/android/app/src/main/java/org/openbot/app/robot/projects/ReadFileTask.java:27-57 — 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 copies of one member (3 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 21+ corresponding lines) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:620 — robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:620-641 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:775-796 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:802-822 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:159 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:159-167 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:162-170 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:422-428 — 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 copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:84 — robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:84-105 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:45-66 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 7+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Bluetooth/BluetoothTable.swift:125 — robot/ios/OpenBot/OpenBot/Controllers/Bluetooth/BluetoothTable.swift:125-131 | robot/ios/OpenBot/OpenBot/Controllers/GameView/GameViewController.swift:200-206 | robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:110-116 | robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift:479-485 | robot/ios/OpenBot/OpenBot/Controllers/Profile/EditProfileFragment.swift:399-405 | robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:343-349 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:393-399 — These 7 members are one piece of code written 7 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 7 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) robot/android/app/src/main/java/org/openbot/app/robot/profile/ProfileFragment.java:70 — robot/android/app/src/main/java/org/openbot/app/robot/profile/ProfileFragment.java:70-80 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:599-607 | robot/android/app/src/main/java/org/openbot/app/robot/projects/ProjectsFragment.java:185-198 — 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 (4 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:484 — robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:484-493 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:550-560 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:566-575 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:581-590 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 9+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:592 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:592-600 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:625-633 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:669-677 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:289-297 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 6+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:174 — robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:174-179 | robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:182-187 | robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:190-195 | robot/ios/OpenBot/OpenBot/Controllers/Settings/SettingsFragment.swift:198-203 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 5+ corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:114 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/Autopilot.java:114-118 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:76-80 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/Navigation.java:104-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:406 — robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:406-418 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BotFunctions.java:433-444 — 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 copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:285 — robot/ios/OpenBot/OpenBot/Controllers/QrScanner/ScannerFragment.swift:285-288 | robot/ios/OpenBot/OpenBot/Utils/extensions/UIViewExtension.swift:253-258 | robot/ios/OpenBot/OpenBot/Utils/extensions/UIViewExtension.swift:352-355 — 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 · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:897 — robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:897-912 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:914-929 | robot/ios/OpenBot/OpenBot/JsEvaluator/JsEvaluator.swift:931-946 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) robot/ios/OpenBot/OpenBot/Data/BluetoothDataController.swift:212 — robot/ios/OpenBot/OpenBot/Data/BluetoothDataController.swift:212-219 | robot/ios/OpenBot/OpenBot/Data/BluetoothDataController.swift:221-228 | robot/ios/OpenBot/OpenBot/Data/BluetoothDataController.swift:230-238 — 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 copies of one member (5 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 4+ corresponding lines) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:121 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:121-124 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:654-657 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:107-110 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:352-355 | robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/RobotInfoFrame.swift:646-649 — These 5 members are one piece of code written 5 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 5 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (69 lines × 2) · ×1
  • Duplicated block (69 lines × 2) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:20 — robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:20-88 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:179-247 — 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 `robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (36–37 lines × 3) · ×1
  • Duplicated block (36–37 lines × 3) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:108 — robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:108-144 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:168-204 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:227-262 — 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 `robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.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.
D4 · Code Duplication · Duplicated block (38–39 lines × 2) · ×1
  • Duplicated block (38–39 lines × 2) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:244 — robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:244-281 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:290-328 — 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 `robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:290` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:105 — robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:105-128 | robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:141-166 — 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 `robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 × 3) · ×1
  • Duplicated block (23 lines × 3) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:250 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:250-272 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:394-416 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:413-435 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:250` 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 (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:427 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:427-445 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift:428-446 — before extracting anything, compare `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift` and `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 180 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18–20 lines × 3) · ×1
  • Duplicated block (18–20 lines × 3) robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:122 — robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:122-141 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:164-183 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:206-223 — 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 `robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16–17 lines × 6) · ×1
  • Duplicated block (16–17 lines × 6) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:263 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:263-278 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:407-422 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:722-737 | robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:426-441 | robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:53-68 | robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:163-179 — there are 6 copies across 5 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:263` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. 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 (15–17 lines × 2) · ×1
  • Duplicated block (15–17 lines × 2) robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:49 — robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:49-63 | REDACTED:45-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. Read the line range as the matched WINDOW rather than a finished unit: at `robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×1
  • Duplicated block (9–10 lines × 3) robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:356 — robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:356-365 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:831-839 | robot/ios/OpenBot/OpenBot/Controllers/runRobot/RunRobot.swift:863-871 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift:356` 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 (7–8 lines × 3) · ×1
  • Duplicated block (7–8 lines × 3) robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:236 — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:236-243 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/DataCollectionController.swift:381-388 | robot/ios/OpenBot/OpenBot/Controllers/FreeRoam/FreeRoamController.swift:700-706 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:236` 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 (4–8 lines × 9) · ×1
  • Duplicated block (4–8 lines × 9) robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:161 — robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:161-164 | robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:190-193 | robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:217-220 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:148-151 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:190-193 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:229-232 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:146-153 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:206-213 | robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift:264-271 — there are 9 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 9 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:315 — robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:315-321 | robot/ios/OpenBot/OpenBot/Controllers/Profile/EditProfileFragment.swift:375-381 | robot/ios/OpenBot/OpenBot/Controllers/Profile/ProfileFragment.swift:233-239 | robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift:431-437 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/ModelManagementTable.swift:315` 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 (4–6 lines × 3) · ×1
  • Duplicated block (4–6 lines × 3) robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:376 — robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:376-381 | robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:399-402 | robot/ios/OpenBot/OpenBot/Controllers/Modes/VehicleControl.swift:97-102 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:381` calls `constraint` and `robot/ios/OpenBot/OpenBot/Controllers/DataCollection/ExpandSetting.swift:402` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (45–50 lines × 3) · ×1
  • Duplicated block (45–50 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:124 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:124-173 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:202-246 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:267-316 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:176` calls `get`, `contentEquals` and `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:319` 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 (56–57 lines × 2) · ×1
  • Duplicated block (56–57 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:109 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:109-165 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:165-220 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/env/ConnectionMonitor.java:82 — robot/android/app/src/main/java/org/openbot/app/robot/env/ConnectionMonitor.java:82-106 | robot/android/app/src/main/java/org/openbot/app/robot/utils/ConnectionUtils.java:83-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (21–23 lines × 3) · ×1
  • Duplicated block (21–23 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:286 — robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:286-308 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:397-417 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:539-561 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:286` 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 (20–21 lines × 2) · ×1
  • Duplicated block (20–21 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/main/SettingsFragment.java:193 — robot/android/app/src/main/java/org/openbot/app/robot/main/SettingsFragment.java:193-212 | robot/android/app/src/main/java/org/openbot/app/robot/main/SettingsFragment.java:214-234 — 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 (17–18 lines × 5) · ×1
  • Duplicated block (17–18 lines × 5) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:140 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:140-157 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:220-236 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:196-212 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:122-138 | robot/android/app/src/main/java/org/openbot/app/robot/robot/RobotInfoFragment.java:61-78 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:573 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:573-590 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:606-623 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:650-667 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:270-287 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `driveMode` to `Enums.DriveMode` in one and `DriveMode` 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 (17 lines × 4) · ×1
  • Duplicated block (17 lines × 4) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:529 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:529-545 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:562-578 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:606-622 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:224-240 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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 `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:529` 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 `speedMode` to `Enums.SpeedMode` in one and `SpeedMode` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (16–17 lines × 3) · ×1
  • Duplicated block (16–17 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:349 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:349-365 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:525-540 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:336-352 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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 `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:349` 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 × 3) · ×1
  • Duplicated block (16 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:117 — robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:117-132 | robot/android/app/src/main/java/org/openbot/app/robot/modelManagement/ModelManagementFragment.java:68-83 | robot/android/app/src/main/java/org/openbot/app/robot/modelManagement/ModelManagementFragment.java:236-251 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:209 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:209-223 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:273-288 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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 `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:209` 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 × 3) · ×1
  • Duplicated block (15 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:168 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:168-182 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:148-162 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:223-237 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:455 — robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:455-467 | robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:497-509 | robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:677-689 — 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 `robot/android/app/src/main/java/org/openbot/app/robot/googleServices/GoogleServices.java:455` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:89 — robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:89-101 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:118-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×1
  • Duplicated block (10 lines × 4) robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:298 — robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:298-307 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:355-364 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:407-416 | robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:551-560 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:298` 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, `robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:296` calls `post` and `robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java:354` 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 (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:397 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:397-405 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:431-440 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:172 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:172-180 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:152-160 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:227-235 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:92-100 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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 `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:172` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:476 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:476-483 | robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:636-643 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:680-687 | robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java:300-307 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 143 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:499 — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:499-505 | robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:573-578 — before extracting anything, compare `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java` and `robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 314 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 `robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:499` 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 (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:122 — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:122-127 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:165-170 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:205-210 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:170-175 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:243-248 | robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java:313-318 — there are 6 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 6 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:128` calls `get`, `contentEquals` and `robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:211` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) policy/openbot/dataloader.py:61 — policy/openbot/dataloader.py:61-76 | policy/openbot/tfrecord.py:62-77 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) policy/openbot/models.py:95 — policy/openbot/models.py:95-104 | policy/openbot/models.py:134-143 | policy/openbot/models.py:217-226 — 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 `policy/openbot/models.py:95` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `policy/openbot/models.py:144` calls `Dropout` and `policy/openbot/models.py:105` 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 (7–10 lines × 2) · ×1
  • Duplicated block (7–10 lines × 2) policy/openbot/train.py:261 — policy/openbot/train.py:261-270 | policy/openbot/train.py:358-364 — 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 `policy/openbot/train.py:261` 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 (19–20 lines × 4) · ×1
  • Duplicated block (19–20 lines × 4) controller/flutter/lib/screens/component/onScreenIcon.dart:198 — controller/flutter/lib/screens/component/onScreenIcon.dart:198-217 | controller/flutter/lib/screens/component/onScreenIcon.dart:226-244 | controller/flutter/lib/screens/tiltingPhoneMode.dart:134-153 | controller/flutter/lib/screens/tiltingPhoneMode.dart:162-181 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `controller/flutter/lib/screens/component/onScreenIcon.dart:198` 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.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 27 typed · 82 plain JS — the untyped files are controller/node-js/client/bot-message-handler.js, controller/node-js/client/buttons.js, REDACTED, controller/node-js/client/error-display.js, controller/node-js/client/index.js, controller/node-js/client/keyboard.js (+76 more).
R10 · Code Duplication · Duplication concentrated across 5 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 5 sibling directories (8 clone groups) open-code/src/components/bottomBar/modelUploadingComponent.js:177 — 8 duplicated blocks under open-code/src/components/ have copies in at least two of the sibling directories bottomBar, drawer, editor, homeComponents, navBar — 5 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (7 clone groups) controller/node-js/client/keyboard.js:23 — 7 duplicated blocks under controller/ have copies in at least two of the sibling directories node-js, web-server — 6 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (239 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (239 matched lines × 2 locations) open-code/src/components/blockly/generator/javascriptGenerator.js:53 — open-code/src/components/blockly/generator/javascriptGenerator.js:53 · open-code/src/components/blockly/generator/pythonGenerator.js:24 — the two spans are one implementation copied and then locally edited — 1517 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (63 lines × 2 locations) · ×1
  • Duplicated block (63 lines × 2 locations) controller/node-js/client/keyboard.js:23 — controller/node-js/client/keyboard.js:23 · controller/web-server/client/keyboardHandlers/keyboard.js:23 — the 2 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 with local edits (63 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (63 matched lines × 2 locations) controller/node-js/server/remote-keyboard.js:25 — controller/node-js/server/remote-keyboard.js:25 · controller/web-server/client/keyboardHandlers/remote_keyboard.js:20 — the two spans are one implementation copied and then locally edited — 291 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (51 identical lines × 2 files) · ×1
  • Wholesale file copy (51 identical lines × 2 files) controller/node-js/server/commands.js:11 — controller/node-js/server/commands.js:11 · controller/web-server/client/keyboardHandlers/commands.js:11 — these 2 files are line-for-line copies of one another — 51 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (46 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (46 matched lines × 2 locations) policy/frontend/src/modals/DatasetModal.tsx:20 — policy/frontend/src/modals/DatasetModal.tsx:20 · policy/frontend/src/modals/PublishModal.tsx:31 — the two spans are one implementation copied and then locally edited — 338 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) open-code/src/utils/constants.js:23 — open-code/src/utils/constants.js:23 · open-code/src/utils/constants.js:64 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication · Duplicated block (35 lines × 2 locations) · ×1
  • Duplicated block (35 lines × 2 locations) open-code/src/components/blockly/blocks/customblocks.js:164 — open-code/src/components/blockly/blocks/customblocks.js:164 · open-code/src/components/blockly/blocks/customblocks.js:203 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (32 lines × 4 locations) · ×1
  • Duplicated block (32 lines × 4 locations) open-code/src/components/blockly/blocks/customblocks.js:359 — open-code/src/components/blockly/blocks/customblocks.js:359 · open-code/src/components/blockly/blocks/customblocks.js:393 · open-code/src/components/blockly/blocks/customblocks.js:427 · open-code/src/components/blockly/blocks/customblocks.js:461 — all 4 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block with local edits (31 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (31 matched lines × 2 locations) controller/node-js/client/buttons.js:10 — controller/node-js/client/buttons.js:10 · controller/web-server/client/keyboardHandlers/buttons.js:10 — the two spans are one implementation copied and then locally edited — 209 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (26 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (26 matched lines × 2 locations) controller/node-js/client/bot-message-handler.js:14 — controller/node-js/client/bot-message-handler.js:14 · controller/web-server/client/keyboardHandlers/bot-message-handler.js:14 — the two spans are one implementation copied and then locally edited — 123 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (25 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (25 matched lines × 2 locations) controller/node-js/client/webrtc.js:24 — controller/node-js/client/webrtc.js:24 · controller/web-server/client/webRTC/webrtc.js:19 — the two spans are one implementation copied and then locally edited — 130 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) open-code/src/services/googleDrive.js:358 — open-code/src/services/googleDrive.js:358 · open-code/src/services/googleDrive.js:386 — 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 (19 lines × 2 locations) · ×1
  • Duplicated block (19 lines × 2 locations) open-code/src/components/bottomBar/modelUploadingComponent.js:177 — open-code/src/components/bottomBar/modelUploadingComponent.js:177 · open-code/src/components/homeComponents/header/editProfileModal.js:176 — the 2 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 (16 lines × 2 locations) · ×1
  • Duplicated block (16 lines × 2 locations) open-code/src/components/blockly/blocks/generalBlocks.js:33 — open-code/src/components/blockly/blocks/generalBlocks.js:33 · open-code/src/components/blockly/toolbox/Toolbox.js:57 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1
  • Duplicated block (15 lines × 2 locations) open-code/src/components/inputComponent/simpleInputComponent.js:164 — open-code/src/components/inputComponent/simpleInputComponent.js:164 · open-code/src/components/inputComponent/simpleInputComponent.js:183 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) open-code/src/components/blockly/toolbox/Toolbox.js:37 — open-code/src/components/blockly/toolbox/Toolbox.js:37 · open-code/src/components/blockly/toolbox/Toolbox.js:62 — 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 with local edits (14 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (14 matched lines × 2 locations) open-code/src/components/homeComponents/header/headerComponents.js:265 — open-code/src/components/homeComponents/header/headerComponents.js:265 · open-code/src/components/navBar/header.js:75 — the two spans are one implementation copied and then locally edited — 81 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) open-code/src/components/bottomBar/modelUploadingComponent.js:42 — open-code/src/components/bottomBar/modelUploadingComponent.js:42 · open-code/src/components/navBar/header.js:101 — the 2 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 with local edits (13 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (13 matched lines × 2 locations) open-code/src/components/homeComponents/header/headerComponents.js:265 — open-code/src/components/homeComponents/header/headerComponents.js:265 · open-code/src/components/homeComponents/header/profileOptionModal.js:58 — the two spans are one implementation copied and then locally edited — 80 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×1
  • Duplicated block (11 lines × 2 locations) open-code/src/components/bottomBar/bottomBar.js:403 — open-code/src/components/bottomBar/bottomBar.js:403 · open-code/src/components/editor/codeEditor.js:32 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (10 lines × 3 locations) · ×1
  • Duplicated block (10 lines × 3 locations) open-code/src/components/blockly/index.js:27 — open-code/src/components/blockly/index.js:27 · open-code/src/components/blockly/index.js:39 · open-code/src/components/blockly/index.js:51 — all 3 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) · ×1
  • Duplicated block (8 lines × 2 locations) policy/frontend/src/pages/ModelsPage.tsx:79 — policy/frontend/src/pages/ModelsPage.tsx:79 · policy/frontend/src/pages/TrainPage.tsx:62 — 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.
R10 · Code Duplication · Duplicated block (7 lines × 3 locations) · ×1
  • Duplicated block (7 lines × 3 locations) open-code/src/components/bottomBar/bottomBar.js:459 — open-code/src/components/bottomBar/bottomBar.js:459 · open-code/src/components/bottomBar/bottomBar.js:469 · open-code/src/components/bottomBar/bottomBar.js:480 — all 3 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 with local edits (5 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (5 matched lines × 2 locations) firmware/web/app.js:110 — firmware/web/app.js:110 · firmware/web/app.js:118 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (5 lines × 2 locations) · ×1
  • Duplicated block (5 lines × 2 locations) open-code/src/components/bottomBar/bottomBar.js:510 — open-code/src/components/bottomBar/bottomBar.js:510 · open-code/src/components/bottomBar/bottomBar.js:515 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R11 · Import Boundaries · Boundary violation [package · ×1
  • Boundary violation [package:test-cross-package-internals] controller/node-js/test/commands.test.js:12 — controller/node-js/test/commands.test.js:12 reaches past another workspace package's public entry into its internals with a relative path (../server/commands.js) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
R2 · Cyclomatic Complexity · Complex function processKey (cyclomatic 39, cognitive 65) · ×1
  • Complex function processKey (cyclomatic 39, cognitive 65) controller/web-server/client/keyboardHandlers/remote_keyboard.js:19 — processKey has cyclomatic complexity 39 and cognitive complexity 65; 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 processKey (cyclomatic 29, cognitive 35) · ×1
  • Complex function processKey (cyclomatic 29, cognitive 35) controller/node-js/server/remote-keyboard.js:24 — processKey has cyclomatic complexity 29 and cognitive complexity 35; 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 RightDrawer (cyclomatic 26, cognitive 25) · ×1
  • Complex function RightDrawer (cyclomatic 26, cognitive 25) open-code/src/components/drawer/drawer.js:22 — RightDrawer has cyclomatic complexity 26 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 ProfileOptionModal (cyclomatic 26, cognitive 16) · ×1
  • Complex function ProfileOptionModal (cyclomatic 26, cognitive 16) open-code/src/components/homeComponents/header/profileOptionModal.js:22 — ProfileOptionModal has cyclomatic complexity 26 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 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 applyLive (cyclomatic 22, cognitive 26) · ×1
  • Complex function applyLive (cyclomatic 22, cognitive 26) firmware/web/app.js:574 — applyLive 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 generateCode (cyclomatic 21, cognitive 49) · ×1
  • Complex function generateCode (cyclomatic 21, cognitive 49) open-code/src/components/bottomBar/bottomBar.js:96 — generateCode has cyclomatic complexity 21 and cognitive complexity 49; 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 UploadCodeButton (cyclomatic 18, cognitive 15) · ×1
  • Complex function UploadCodeButton (cyclomatic 18, cognitive 15) open-code/src/components/bottomBar/bottomBar.js:368 — UploadCodeButton has cyclomatic complexity 18 and cognitive complexity 15; 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 renderRobot (cyclomatic 17, cognitive 16) · ×1
  • Complex function renderRobot (cyclomatic 17, cognitive 16) firmware/web/app.js:386 — renderRobot has cyclomatic complexity 17 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 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 Card (cyclomatic 15, cognitive 14) · ×1
  • Complex function Card (cyclomatic 15, cognitive 14) open-code/src/components/homeComponents/myProjects/card.js:30 — Card has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 EditProfileModal (cyclomatic 15, cognitive 10) · ×1
  • Complex function EditProfileModal (cyclomatic 15, cognitive 10) open-code/src/components/homeComponents/header/editProfileModal.js:22 — EditProfileModal has cyclomatic complexity 15 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.
R2 · Cyclomatic Complexity · Complex function handle (cyclomatic 13, cognitive 14) · ×1
  • Complex function handle (cyclomatic 13, cognitive 14) controller/web-server/client/keyboardHandlers/bot-message-handler.js:19 — handle has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function BottomBar (cyclomatic 13, cognitive 11) · ×1
  • Complex function BottomBar (cyclomatic 13, cognitive 11) open-code/src/components/bottomBar/bottomBar.js:30 — BottomBar has cyclomatic complexity 13 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function applyBlocker (cyclomatic 12, cognitive 12) · ×1
  • Complex function applyBlocker (cyclomatic 12, cognitive 12) firmware/web/app.js:190 — applyBlocker has cyclomatic complexity 12 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 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 clickedButton (cyclomatic 11, cognitive 11) · ×1
  • Complex function clickedButton (cyclomatic 11, cognitive 11) open-code/src/components/bottomBar/bottomBar.js:215 — clickedButton has cyclomatic complexity 11 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 CreateNewProjectModal (cyclomatic 11, cognitive 10) · ×1
  • Complex function CreateNewProjectModal (cyclomatic 11, cognitive 10) open-code/src/components/homeComponents/myProjects/newProjectButton.js:117 — CreateNewProjectModal has cyclomatic complexity 11 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.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 9) · ×1
  • Complex function (anonymous) (cyclomatic 11, cognitive 9) firmware/web/app.js:314 — (anonymous) has cyclomatic complexity 11 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.
R3 · Large Files · open-code/src/components/blockly/blocks/customblocks.js · ×1
  • open-code/src/components/blockly/blocks/customblocks.js: 953 lines of code open-code/src/components/blockly/blocks/customblocks.js:1 — open-code/src/components/blockly/blocks/customblocks.js has 953 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · firmware/web/app.js · ×1
  • firmware/web/app.js: 706 lines of code firmware/web/app.js:1 — firmware/web/app.js has 706 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · open-code/src/components/bottomBar/bottomBar.js · ×1
  • open-code/src/components/bottomBar/bottomBar.js: 518 lines of code open-code/src/components/bottomBar/bottomBar.js:1 — open-code/src/components/bottomBar/bottomBar.js has 518 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · open-code/src/services/googleDrive.js · ×1
  • open-code/src/services/googleDrive.js: 465 lines of code open-code/src/services/googleDrive.js:1 — open-code/src/services/googleDrive.js has 465 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · open-code/src/services/workspace.js · ×1
  • open-code/src/services/workspace.js: 408 lines of code open-code/src/services/workspace.js:1 — open-code/src/services/workspace.js has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R8 · Dependency Hygiene · Unused dependency 'cookie-parser' · ×1
  • Unused dependency 'cookie-parser' — Declared in controller/node-js/server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'debug' · ×1
  • Unused dependency 'debug' — Declared in controller/node-js/server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'ejs' · ×1
  • Unused dependency 'ejs' — Declared in controller/node-js/server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'express' · ×1
  • Unused dependency 'express' — Declared in controller/node-js/server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'http-errors' · ×1
  • Unused dependency 'http-errors' — Declared in controller/node-js/server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'morgan' · ×1
  • Unused dependency 'morgan' — Declared in controller/node-js/server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'net' · ×1
  • Unused dependency 'net' — Declared in controller/node-js/server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@emotion/react' · ×1
  • Unused dependency '@emotion/react' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@emotion/styled' · ×1
  • Unused dependency '@emotion/styled' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@firebase/firestore' · ×1
  • Unused dependency '@firebase/firestore' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency '@testing-library/react' · ×1
  • Unused dependency '@testing-library/react' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'crypto-browserify' · ×1
  • Unused dependency 'crypto-browserify' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'firebase-admin' · ×1
  • Unused dependency 'firebase-admin' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'js-tokens' · ×1
  • Unused dependency 'js-tokens' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'jsonwebtoken' · ×1
  • Unused dependency 'jsonwebtoken' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'moment' · ×1
  • Unused dependency 'moment' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'react-dev-utils' · ×1
  • Unused dependency 'react-dev-utils' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'react-firebase-hooks' · ×1
  • Unused dependency 'react-firebase-hooks' — Declared in open-code/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity controller/web-server/client/index.html:14 — `https://accounts.google.com/gsi/client` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository.
Minor — 146 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×72
  • Orphaned file robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/PopupWindowView.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ArCore.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Data/DataLogger.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Controllers/Modes/VehicleControl.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Data/GameController.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/tflite/Detector.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Data/BluetoothDataController.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Data/WebRTC/WebRTCClient.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Controllers/GameView/GameViewController.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/BottomSheet.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/android/app/src/main/java/org/openbot/app/robot/main/MainActivity.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file controller/flutter/lib/screens/tiltingPhoneMode.dart:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Controllers/WebServer/ServerWebrtcDelegates.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Utils/Constants.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/tflite/Network.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/ios/OpenBot/OpenBot/Controllers/RobotInfo/CheckBox.swift:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/android/app/src/main/java/org/openbot/app/robot/server/ServerCommunication.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/android/app/src/main/java/org/openbot/app/robot/env/RtspServer.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file robot/android/app/src/main/java/org/openbot/app/robot/utils/YuvToRgbConverter.kt: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.
  • + 47 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×24
  • Duplicated predicate controller/flutter/lib/screens/component/onScreenIcon.dart:46 — `typeOfFragment == "Autopilot" || typeOfFragment == "ObjectDetection"` appears character-identically in 2 files — controller/flutter/lib/screens/component/onScreenIcon.dart, controller/flutter/lib/screens/tiltingPhoneMode.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 robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java:423 — `binding != null && binding.autoSwitch.isChecked()` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/autopilot/AutopilotFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:128 — `classId > -1 && labels.get(classId).contentEquals(className)` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java, robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:171 — `classId > -1 && labels.get(classId).contentEquals(classNameFirst)` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java, robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java:175 — `classId > -1 && labels.get(classId).contentEquals(classNameSecond)` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV4.java, robot/android/app/src/main/java/org/openbot/app/robot/tflite/DetectorYoloV5.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:138 — `connectionType != null && connectionType.equals("Bluetooth")` appears character-identically in 3 files — robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/robot/RobotInfoFragment.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java:135 — `connectionType != null && connectionType.equals("USB")` appears character-identically in 3 files — robot/android/app/src/main/java/org/openbot/app/robot/logging/LoggerFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/robot/FreeRoamFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/robot/RobotInfoFragment.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:189 — `itemList.length == 2 && FormatUtils.isNumeric(itemList[0]) && FormatUtils.isNumeric(itemList[1])` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java:499 — `location != null && result.getConfidence() >= MINIMUM_CONFIDENCE_TF_OD_API` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/objectNav/ObjectNavFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:591 — `modelAdapter != null && modelAdapter.getPosition(model) != -1` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java:573 — `modelAdapter != null && modelAdapter.getPosition(model) == -1` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/common/ControlsFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/original/CameraActivity.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:89 — `newState == BottomSheetBehavior.STATE_EXPANDED || newState == BottomSheetBehavior.STATE_HALF_EXPANDED` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/projects/ProjectsFragment.java. 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 robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java:352 — `orientation == Configuration.ORIENTATION_LANDSCAPE || orientation == Configuration.ORIENTATION_PORTRAIT` appears character-identically in 2 files — robot/android/app/src/main/java/org/openbot/app/robot/projects/BarCodeScannerFragment.java, robot/android/app/src/main/java/org/openbot/app/robot/projects/BlocklyExecutingFragment.java. 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 open-code/src/components/homeComponents/cookies/cookies.js:18 — `/iPad|iPhone|iPod/.test(navigator.userAgent) && !window.MSStream` appears character-identically in 2 files — open-code/src/components/homeComponents/cookies/cookies.js, open-code/src/components/homeComponents/myProjects/newProjectButton.js. 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 controller/node-js/server/commands.js:120 — `last.driveCmd.l === current.driveCmd.l && last.driveCmd.r === current.driveCmd.r` appears character-identically in 2 files — controller/node-js/server/commands.js, controller/web-server/client/keyboardHandlers/commands.js. 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 open-code/src/components/bottomBar/bottomBar.js:417 — `popUpRef.current && !popUpRef.current.contains(event.target)` appears character-identically in 2 files — open-code/src/components/bottomBar/bottomBar.js, open-code/src/components/homeComponents/header/headerComponents.js. 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 open-code/src/components/bottomBar/modelUploadingComponent.js:190 — `theme === Themes.dark && styles.darkEditProfileModal` appears character-identically in 2 files — open-code/src/components/bottomBar/modelUploadingComponent.js, open-code/src/components/homeComponents/header/editProfileModal.js. 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 robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:185 — `classId > -1 && (classA == labels[classId] || classB == labels[classId])` appears character-identically in 2 files — robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift, robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift:143 — `classId > -1 && className == labels[classId]` appears character-identically in 2 files — robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV4.swift, robot/ios/OpenBot/OpenBot/tflite/DetectorFloatYoloV5.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:160 — `control.getRight() != vehicleControl.getRight() || control.getLeft() != vehicleControl.getLeft()` appears character-identically in 7 files — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift, robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift, robot/ios/OpenBot/OpenBot/Controllers/PointGoalNavigation/PointGoalFragment.swift, robot/ios/OpenBot/OpenBot/Controllers/Project/ProjectFragement.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:94 — `currentOrientation == .portrait || currentOrientation == .portraitUpsideDown` appears character-identically in 3 files — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift, robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift, robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingFragment.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:84 — `grantedScopes == nil || !grantedScopes!.contains(driveScope)` appears character-identically in 2 files — robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift, REDACTED. 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 robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:524 — `threadLabel.text == "1" || threadLabel.text == "N/A"` appears character-identically in 2 files — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift, robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift:511 — `threadLabel.text == "9" || threadLabel.text == "N/A"` appears character-identically in 2 files — robot/ios/OpenBot/OpenBot/Controllers/Autopilot/ExpandedAutoPilot.swift, robot/ios/OpenBot/OpenBot/Controllers/ObjectTracking/ObjectTrackingSettings.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.
D24 · Comment Value · redundant comment · ×12
  • redundant comment controller/web-server/client/webRTC/webrtc.js:18 — "WebRTC type" repeats the code it sits on: 3 of its 3 words (web, rtc, type) are already in `switch (webRtcEvent.type)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/components/blockly/BlocklyComponent.jsx:230 — "Add change listener to the workspace" repeats the code it sits on: 4 of its 4 words (add, change, listener, workspace) are already in `primaryWorkspace.current.addChangeListener(handleWorkspaceChange);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/components/bottomBar/bottomBar.js:124 — "filtering multiple objectTracking connected blocks" repeats the code it sits on: 5 of its 6 words (filtering, multiple, object, tracking, blocks) are already in `let multipleObjectTrackingEnabledBlocks = multipleObjectTracking?.filter(obj => obj.disabled === false);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/components/bottomBar/bottomBar.js:125 — "handling error for multiple ai blocks" repeats the code it sits on: 4 of its 5 words (handling, multiple, ai, blocks) are already in `let isAIBlocksAdjacent = handlingMultipleAIBlocks(start)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/components/bottomBar/bottomBar.js:171 — "Call function to upload xml data to Google Drive" repeats the code it sits on: 6 of its 7 words (call, upload, xml, data, google, drive) are already in `uploadToGoogleDrive(data, "xml")`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/components/bottomBar/modelUploadingComponent.js:71 — "function to handle model type and class dependency on type" repeats the code it sits on: 5 of its 6 words (handle, model, type, class, dependency) are already in `const handleTypeMap = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/components/homeComponents/header/editProfileModal.js:95 — "handle name change" repeats the code it sits on: 3 of its 3 words (handle, name, change) are already in `function handleNameChange(name)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/components/homeComponents/myProjects/newProjectButton.js:71 — "function to handle project name change" repeats the code it sits on: 4 of its 5 words (handle, project, name, change) are already in `function handleProjectNameChange(name)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/services/googleDrive.js:87 — "Check if a file with the specified fileId exists" repeats the code it sits on: 4 of its 5 words (check, file, id, exists) are already in `fileExistWithFileID = await checkFileExistsInFolder(folderId, data.projectName, 'xml')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/services/googleDrive.js:90 — "Check if a file with the specified fileId exists" repeats the code it sits on: 4 of its 5 words (check, file, id, exists) are already in `fileExistWithFileID = await checkFileExistsInFolder(folderId, getCurrentProject().projectName, 'js')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/services/googleDrive.js:93 — "Check if a file with the specified fileId exists" repeats the code it sits on: 4 of its 5 words (check, file, id, exists) are already in `fileExistWithFileID = await checkFileExistsInFolder(folderId, "config", 'json')`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment open-code/src/services/workspace.js:75 — "set restProjects as all project in local" repeats the code it sits on: 5 of its 5 words (set, rest, projects, project, local) are already in `localStorage.setItem(localStorageKeys.allProjects, JSON.stringify(restProjects))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D30 · Dependency Vulnerabilities · Low CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
R7 · Dead Code · Unused export 'default' · ×2
  • Unused export 'default' open-code/src/components/blockly/fields/DateField.jsx:39 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'default' open-code/src/services/firebase.js:39 — Nothing imports this binding — it is safe to review for removal.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/PointGoalNavigationFragment.java. Pair on, review, or document these before any departure.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found robot/ios/OpenBot/OpenBot.xcodeproj/project.pbxproj:1 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `robot/ios/OpenBot/OpenBot.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency · `dummyProjectID` spells `ID` where 44 names in the project spell it `Id` · ×1
  • `dummyProjectID` spells `ID` where 44 names in the project spell it `Id` robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:569 — 44 of 45 names in project repository spell the token `Id` (44 of 45; unit: names in project repository containing `Id`). Peers: Authentication.returnFileId (robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:30); Authentication.googleSignInFunc(clientId) (robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:43); Authentication.getOPenBotFolderId (robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:119); Authentication.download(fileId) (robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:178); Authentication.getFilesInFolder(folderId) (robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:272). Rename to `dummyProjectId`. [rule N6]
D21 · Naming Consistency · `leadingAnchorOFTable` spells `OF` where 35 names in the project spell it `Of` · ×1
  • `leadingAnchorOFTable` spells `OF` where 35 names in the project spell it `Of` robot/ios/OpenBot/OpenBot/Controllers/ModelManagement/BottomSheet.swift:14 — 35 of 36 names in project repository spell the token `Of` (35 of 36; unit: names in project repository containing `Of`). Peers: Authentication.getIdOfDriveFile (robot/ios/OpenBot/OpenBot/Authentication/Authentication.swift:348); AutopilotFragment.numberOfThreads (robot/ios/OpenBot/OpenBot/Controllers/Autopilot/AutopilotFragment.swift:12); BluetoothTable.numberOfSections (robot/ios/OpenBot/OpenBot/Controllers/Bluetooth/BluetoothTable.swift:55); BluetoothTable.tableView(numberOfRowsInSection) (robot/ios/OpenBot/OpenBot/Controllers/Bluetooth/BluetoothTable.swift:59); CameraController.widthOfTrainingImage (robot/ios/OpenBot/OpenBot/Controllers/CameraController.swift:19). Rename to `leadingAnchorOfTable`. [rule N6]
D21 · Naming Consistency · `fileExistWithFileID` spells `ID` where 19 names in the project spell it `Id` · ×1
  • `fileExistWithFileID` spells `ID` where 19 names in the project spell it `Id` open-code/src/services/googleDrive.js:110 — 19 of 20 names in project repository spell the token `Id` (19 of 20; unit: names in project repository containing `Id`). Peers: index.sendId (controller/web-server/client/index.js:126); server.askIdOfClient (controller/web-server/server/server.js:65); server.joinRoom(roomId) (controller/web-server/server/server.js:69); server.relayToPeer(roomId) (controller/web-server/server/server.js:114); googleDrive.uploadFileToFolder(folderId) (open-code/src/services/googleDrive.js:37). Rename to `fileExistWithFileId`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 3 of 15 project(s) overshoot their size bounds, lowering Project Cohesion to 6.0/10. The most over is `robot/ios/OpenBot` (20167 LoC, 208 module-visible types across 37 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 72 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: robot/ios/OpenBot/OpenBot/Utils/extensions/CVPixelBuffer.swift, robot/android/app/src/main/java/org/openbot/app/robot/pointGoalNavigation/ArCore.java, REDACTED, robot/ios/OpenBot/OpenBot/tflite/Detector.swift, robot/ios/OpenBot/OpenBot/tflite/DetectorDefault.swift, robot/android/app/src/main/java/org/openbot/app/robot/main/MainActivity.java, REDACTED, controller/flutter/lib/screens/tiltingPhoneMode.dart (and 64 more) (81 orphaned of 164 analysed files in total, 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; 164 of the 311 production source files in this repository met that bar). 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 1/6 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `controller/flutter`, `controller/flutter/ios`, `controller/node-js/server`, `controller/python`, `robot/ios/OpenBot`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:9 — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 14 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 · No dependency-update automation · ×1
  • No dependency-update automation controller/node-js/package.json:17 — `controller/node-js/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code · Unused export 'FirebaseStorage' · ×1
  • Unused export 'FirebaseStorage' controller/web-server/client/firebase/authentication.js:21 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'conditionalLoops' · ×1
  • Unused export 'conditionalLoops' open-code/src/components/blockly/blocks/generalBlocks.js:31 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'handleUserRestriction' · ×1
  • Unused export 'handleUserRestriction' open-code/src/services/workspace.js:416 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'buttonColor' · ×1
  • Unused export 'buttonColor' open-code/src/utils/color.js:15 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused module-local declaration 'getDocDetails' · ×1
  • Unused module-local declaration 'getDocDetails' controller/web-server/client/firebase/APIs.js:36 — 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.
R8 · Dependency Hygiene · Test-only dependency '@testing-library/react' in production deps · ×1
  • Test-only dependency '@testing-library/react' in production deps policy/frontend/package.json:6 — Only test files import it (first: policy/frontend/src/App.test.js:1) — move it to devDependencies.
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/13 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.
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/24 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
X7 · Silent fallback defaults · Pending state with no failure state · ×1
  • Pending state with no failure state open-code/src/components/homeComponents/myProjects/newProject.js:72 — The view draws `<div className= >` under `( loader || projects ) && ! deleteLoader`, but `projects` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
Minor — 2 finding(s)
D24 · Comment Value · doc comments repeat the names · ×2
  • doc comments repeat the names open-code/src/components/bottomBar/bottomBar.js:502 — 3 of 112 documented parameters and 6 of 123 summaries in `open-code` only repeat the member or parameter name (e.g. "Undo redo" for `UndoRedo`). 86 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names controller/web-server/client/firebase/APIs.js:8 — 0 of 5 documented parameters and 0 of 5 summaries in `web-server` only repeat the member or parameter name (e.g. "" for `serverStartTime`). 5 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.

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-97c1aca066ff45cfaa4f132801986155/history.json --exit-code 0 --source .0artifacts/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-97c1aca066ff45cfaa4f132801986155/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 .67artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .95artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .2artifacts/raw/semgrep-gdpr.json
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1dc3a-41c4-7bfb-a866-bdc794b2d944 · 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