Public report of lycorp-jp/sim-use, published 15 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, 15 November 2026, 02:33 UTC · Survey ID cd_0a9e3efb3d9d4003a0ca55b2b2bddca4

lycorp-jp/sim-use

Measured 15 November 2026, 02:30 UTC, at code version f506259

CAI score 65out of 100 Strong
CriticalWeakAdequateStrongExemplary
Up 6 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: 41,236 lines of product code in 13 projects, tests not counted · Estimated rebuild effort: about 0.6 person-years · Weakest lens: Code Health, 53

Findings by how serious they are

12 critical 352 serious 25 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
15 November 2026, 02:30 UTC

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

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

55of 55 dimensions measured by tools.
379of 389 findings point to an exact file and line, so you can open each one in the code. The other 10 concern the repository as a whole, such as missing documentation.
55dimensions across 6 lenses, read from 41,236 lines of product code in 13 projects.
Chapters

Executive summary

lycorp-jp/sim-use meets our standard for a preview release. It scores 65 out of 100 and is rated Strong, and all 12 of its critical findings are security problems in the build pipeline and in the packages it uses.

Code Health, at 53, is the weakest lens and counts most in the score. The best first steps are simplifying the most tangled functions and splitting the oversized files, each worth about 6 points. Raising Code Health to 67 would lift the score to about 71.

Eleven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One known security hole in a package the code depends on can be used by attackers. Pinning each tool to an exact version and updating the vulnerable packages would close both risks.

The product code is 41,236 lines, about €88,000 to rebuild.

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

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

If Code Health rose from 53 to 67, the lowest score rated Strong, the score would rise from 65 to about 71.

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

These 85 critical or serious findings weren't in the previous survey, on 29 October 2026.

  • Cognitive Complexity · BridgeClient.verifiedEndpoint (cognitive 25) Sources/AndroidBackend/Bridge/BridgeClient.swift
  • Cognitive Complexity · AuthTokenFetcher.fetchEndpoint (cognitive 21) Sources/AndroidBackend/Adb/AuthTokenFetcher.swift
  • Cognitive Complexity · AuthTokenFetcher.parseEndpoint (cognitive 20) Sources/AndroidBackend/Adb/AuthTokenFetcher.swift
  • God Classes · TooManyMethods: BridgeClient Sources/AndroidBackend/Bridge/BridgeClient.swift
  • Code Duplication · Near-duplicate member family (3 members, 24 shared lines) Sources/AndroidBackend/Adb/Adb.swift
  • Code Duplication · Edited copy of a member (78 corresponding lines) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift
  • Code Duplication · Edited copy of a member (44 corresponding lines) Sources/SimUseCore/SelectorFrameFilter.swift
  • Code Duplication · Edited copy of a member (29 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift
  • Code Duplication · Edited copy of a member (29 corresponding lines) Sources/iOSSimBackend/Sim/ResizableAppSession.swift
  • Code Duplication · Edited copy of a member (28 corresponding lines) Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift
  • Code Duplication · Edited copy of a member (29 corresponding lines) Sources/iOSSimBackend/Verbs/IOSSimButtonCommand.swift
  • Code Duplication · Edited copy of a member (31 corresponding lines) Sources/iOSSimBackend/A11y/OrientationCalibrator.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) Sources/iOSSimBackend/Normalizer/ListDetector.swift
  • Code Duplication · Edited copy of a member (29 corresponding lines) Sources/iOSSimBackend/Verbs/IOSSimKeyComboCommand.swift
  • Code Duplication · Edited copy of a member (16 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift
  • Code Duplication · Edited copy of a member (21 corresponding lines) Sources/iOSSimBackend/A11y/DisplayOrientation.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidSelector.swift
  • Code Duplication · Edited copy of a member (19 corresponding lines) Sources/SimUseVideo/MPEGTSMuxer.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) Sources/iOSSimBackend/Sim/BundleIdentifierResolver.swift
  • Code Duplication · Edited copy of a member (17 corresponding lines) Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidSelector.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/AndroidBackend/Bridge/BridgeClient.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Sources/SimUseCore/SwipeCoordinates.swift
  • Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) Sources/iOSSimBackend/Verbs/IOSSimMultiTouchCommand.swift
  • Code Duplication · Edited copy of a member (22 corresponding lines) Sources/iOSSimBackend/A11y/AccessibilityPoller.swift
  • Code Duplication · Edited copy of a member (14 corresponding lines) Sources/iOSSimBackend/A11y/SoftKeyboardDetector.swift
  • Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) Sources/SimUse/Commands/Devices.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) Sources/SimUseCore/SelectorTextMatcher.swift
  • Code Duplication · Edited copies of one member (5 members, 12+ corresponding lines) Sources/AndroidBackend/Normalizer/AndroidSelector.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) Sources/iOSSimBackend/Sim/ResizableAppSession.swift
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) Sources/SimUseCore/Daemon/DaemonProtocol.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) Sources/SimUseVideo/VideoRecordingOptions.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/SimUseCore/Daemon/DaemonCommand.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift
  • Code Duplication · Edited copy of a member (11 corresponding lines) Sources/iOSSimBackend/Sim/ResizableAppSession.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt
  • Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) Sources/AndroidBackend/Bridge/BridgeClient.swift
  • Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) Sources/AndroidBackend/Verbs/AndroidGestureCommand.swift
  • Code Duplication · Edited copy of a member (13 corresponding lines) Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Sources/SimUseCore/JSONEnvelopeWriter.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Sources/iOSSimBackend/A11y/DisplayOrientation.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/SimUseVideo/H264MuxingPipeline.swift
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/iOSSimBackend/Verbs/IOSSimBatchCommand.swift
  • Code Duplication · Edited copy of a member (12 corresponding lines) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/iOSDeviceBackend/Domain/DeviceTreeFetcher.swift
  • Code Duplication · Edited copy of a member (19 corresponding lines) Sources/iOSSimBackend/Sim/Setup.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/GestureHandler.kt
  • Code Duplication · Edited copy of a member (6 corresponding lines) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift
  • Code Duplication · Edited copy of a member (10 corresponding lines) Sources/SimUse/Commands/Paste.swift
  • Code Duplication · Edited copy of a member (7 corresponding lines) Sources/SimUseCore/Daemon/DaemonProtocol.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/AndroidBackend/Verbs/AndroidPasteCommand.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Sources/AndroidBackend/Normalizer/TruncationHelpers.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Sources/SimUseCore/GesturePreset.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/SimUseVideo/H264PassthroughRecorder.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Sources/AndroidBackend/Bridge/BridgeSession.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Sources/AndroidBackend/Bridge/BridgeSession.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Sources/AndroidBackend/Bridge/ElementNode.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Sources/SimUseCore/SelectorFrameFilter.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/SimUse/Commands/Swipe.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/SimUse/Commands/Touch.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Sources/AndroidBackend/Verbs/AndroidTouchCommand.swift
  • Code Duplication · Edited copy of a member (8 corresponding lines) Sources/iOSSimBackend/Sim/DevicePosture.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/SimUse/Commands/DescribeUI.swift
  • Code Duplication · Edited copy of a member (6 corresponding lines) Sources/SimUse/Viewer/ViewerAPIHandlers.swift
  • Code Duplication · Edited copy of a member (4 corresponding lines) Sources/AndroidBackend/Verbs/AndroidAppStateCommand.swift
  • Code Duplication · Edited copy of a member (3 corresponding lines) Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift
  • Code Duplication · Edited copy of a member (5 corresponding lines) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift
  • Code Duplication · Edited copy of a member (9 corresponding lines) Sources/SimUse/Commands/MultiTouch.swift
  • Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) Sources/SimUse/Commands/SpikeDaemon.swift
  • Code Duplication · Duplicated block (24–27 lines × 3) Sources/AndroidBackend/Adb/Adb.swift
  • Code Duplication · Duplicated block (13 lines × 2) Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift
  • Code Duplication · Duplicated block (8–11 lines × 2) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift
  • Code Duplication · Duplicated block (9 lines × 2) Sources/iOSSimBackend/Normalizer/ListDetector.swift
  • Test Quality · No assertions: testRecentSessionWithoutOwnedForwardRequiresDiscovery Tests/AndroidBackendTests/BridgeConnectionScopingTests.swift
  • Churn × Complexity Hotspots · Repeated repair: Sources/AndroidBackend/Bridge/BridgeClient.swift Sources/AndroidBackend/Bridge/BridgeClient.swift
  • Churn × Complexity Hotspots · Repeated repair: Sources/AndroidBackend/Bridge/BridgeSession.swift Sources/AndroidBackend/Bridge/BridgeSession.swift
  • Churn × Complexity Hotspots · Repeated repair: Sources/AndroidBackend/Verbs/AndroidDeviceController.swift Sources/AndroidBackend/Verbs/AndroidDeviceController.swift
  • Churn × Complexity Hotspots · Repeated repair: Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift
  • Churn × Complexity Hotspots · Repeated repair: Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift Sources/iOSSimBackend/Batch/Command+BatchConvertible.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: 38 findings

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

  • Cyclomatic Complexity · App.App (cyclomatic 74) Tools/Viewer/src/App.tsx
  • Cyclomatic Complexity · Details.Details (cyclomatic 22) Tools/Viewer/src/Details.tsx
  • Cognitive Complexity · App.App (cognitive 89) Tools/Viewer/src/App.tsx
  • Cognitive Complexity · Details.Details (cognitive 21) Tools/Viewer/src/Details.tsx
  • God Classes · FunctionTooLong: App.App Tools/Viewer/src/App.tsx
  • God Classes · FunctionTooLong: Details.Details Tools/Viewer/src/Details.tsx
  • Code Duplication · Near-duplicate member family (3 members, 21 shared lines) Sources/AndroidBackend/Adb/Adb.swift
  • Code Duplication · Near-duplicate member pair (37 shared lines) Sources/SimUseCore/SelectorFrameFilter.swift
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) Playgrounds/iOS/SimUsePlayground/Views/ButtonTestView.swift
  • Code Duplication · Duplicated block (21–24 lines × 3) Sources/AndroidBackend/Adb/Adb.swift
  • Code Duplication · Duplicated block (17 lines × 2) Playgrounds/iOS/SimUsePlayground/Views/ButtonTestView.swift
  • Code Duplication · Duplicated block (15 lines × 4) Playgrounds/iOS/SimUsePlayground/Views/PasteTestView.swift
  • Code Duplication · Duplicated block (14 lines × 2) Playgrounds/iOS/SimUsePlayground/Views/TapTestView.swift
  • Code Duplication · Duplicated block (14 lines × 2) Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift
  • Code Duplication · Duplicated block (13 lines × 2) Playgrounds/iOS/SimUsePlayground/Views/TapTestView.swift
  • Code Duplication · Duplicated block (12 lines × 2) Sources/AndroidBackend/Bridge/ElementNode.swift
  • Code Duplication · Duplicated block (12 lines × 2) Sources/SimUseCore/SelectorFrameFilter.swift
  • Code Duplication · Duplicated block (10–11 lines × 6) Playgrounds/iOS/SimUsePlayground/Views/ButtonTestView.swift
  • Code Duplication · Duplicated block (8–11 lines × 2) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift
  • Code Duplication · Duplicated block (8 lines × 2) Sources/iOSSimBackend/HID/KeyCode.swift
  • Code Duplication · Duplicated block (6 lines × 2) Sources/iOSSimBackend/Normalizer/ListDetector.swift
  • Code Duplication · Duplicated block (5 lines × 2) Playgrounds/iOS/SimUsePlayground/Views/TapTestView.swift
  • Code Duplication · Duplicated block (5 lines × 2) Sources/iOSSimBackend/Sim/ResizableAppSession.swift
  • Code Duplication · Duplicated block (6 lines × 2) Sources/AndroidBackend/Bridge/ElementNode.swift
  • Code Duplication · Duplicated block (5 lines × 3) Sources/AndroidBackend/Adb/Adb.swift
  • Code Duplication · Duplicated block (5 lines × 2) Sources/iOSSimBackend/HID/KeyCode.swift
  • Churn × Complexity Hotspots · Hotspot: Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift
  • Churn × Complexity Hotspots · Hotspot: Sources/iOSSimBackend/Sim/ResizableAppSession.swift Sources/iOSSimBackend/Sim/ResizableAppSession.swift
  • Churn × Complexity Hotspots · Hotspot: Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift
  • Churn × Complexity Hotspots · Hotspot: Playgrounds/iOS/SimUsePlayground/ContentView.swift Playgrounds/iOS/SimUsePlayground/ContentView.swift
  • Churn × Complexity Hotspots · Repeated repair: Sources/iOSSimBackend/HID/HIDInteractor.swift Sources/iOSSimBackend/HID/HIDInteractor.swift
  • Churn × Complexity Hotspots · Repeated repair: Sources/iOSSimBackend/A11y/LegacyAccessibilityBridge.swift Sources/iOSSimBackend/A11y/LegacyAccessibilityBridge.swift
  • Churn × Complexity Hotspots · Repeated repair: Sources/iOSSimBackend/Verbs/IOSSimTypeCommand.swift Sources/iOSSimBackend/Verbs/IOSSimTypeCommand.swift
  • Forms & labels · <input> without a programmatic label Tools/Viewer/src/App.tsx
  • Keyboard semantics · Click handler on a non-interactive <g> Tools/Viewer/src/Canvas.tsx
  • Keyboard semantics · Click handler on a non-interactive <code> Tools/Viewer/src/Details.tsx
  • Keyboard semantics · Click handler on a non-interactive <span> Tools/Viewer/src/Details.tsx
  • A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €88,000 · Estimate
Cost to rebuild€29,000 to €150,000, for 489 to 1,550 hours of work, about 0.6 person-years for 1 to 2 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.9 at a score of 65. 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: 41,236 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 5 finding(s) in Cyclomatic Complexity.
Raises the score by about 6 points · Medium effort · Cyclomatic Complexity
2
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Raises the score by about 6 points · Medium effort · Large Files
3
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Raises the score by about 5 points · Medium effort · Security & performance tooling

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 €88,000 to build again, about 0.6 person-years of work. Its weakest lens is Code Health, at 53 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 5 finding(s) in Cyclomatic Complexity. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort, because it clears the 5 Cyclomatic Complexity findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch AndroidBackend AndroidBackend SimUseCore SimUseCore AndroidBackend->SimUseCore SimUseVideo SimUseVideo AndroidBackend->SimUseVideo SimUse SimUse SimUse->AndroidBackend SimUse->SimUseCore SimUse->SimUseVideo iOSDeviceBackend iOSDeviceBackend SimUse->iOSDeviceBackend iOSSimBackend iOSSimBackend SimUse->iOSSimBackend SimUseLinux SimUseLinux SimUseLinux->AndroidBackend SimUseLinux->SimUseCore SimUsePlayground SimUsePlayground SimUseVideo->SimUseCore iOSDeviceBackend->SimUseCore iOSSimBackend->SimUseCore iOSSimBackend->SimUseVideo sim-use-device-bridge sim-use-device-bridge sim-use-device-bridge:app sim-use-device-bridge:app sim-use-playground sim-use-playground sim-use-playground:app sim-use-playground:app sim-use-viewer sim-use-viewer

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.

37 modules, with 44 dependencies between them. 2 loops run through 6 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Tools.Viewer.src.Details2 Tools.Viewer.src.types3 com.linecorp.simuse.devicebridge.config4 com.linecorp.simuse.devicebridge.config.AuthManager5 com.linecorp.simuse.devicebridge.handler.CaptureHandler6 com.linecorp.simuse.devicebridge.handler.GestureHandler7 com.linecorp.simuse.devicebridge.handler.InputHandler8 com.linecorp.simuse.devicebridge.handler.KeyboardStateHandler9 com.linecorp.simuse.devicebridge.handler.PasteHandler10 com.linecorp.simuse.devicebridge.model.ElementNode11 com.linecorp.simuse.devicebridge.server.ActionRouter12 com.linecorp.simuse.devicebridge.server.HttpServer13 com.linecorp.simuse.devicebridge.service.BridgeKeepAliveService14 com.linecorp.simuse.devicebridge.service.SimuseContentProvider15 com.linecorp.simuse.playground16 com.linecorp.simuse.playground.MainActivity.RowAdapter17 skills.sim-use.scripts.preflight18 Tools.Viewer.src.Canvas19 com.linecorp.simuse.devicebridge.handler.InputHandler.KeyResult20 com.linecorp.simuse.devicebridge.handler.PasteHandler.Result21 com.linecorp.simuse.devicebridge.model22 com.linecorp.simuse.devicebridge.service.SimuseAccessibilityService23 com.linecorp.simuse.playground.MainActivity24 iOSSimBackend25 skills.sim-use.scripts26 SimUseVideo27 Tools.Viewer.src28 com.linecorp.simuse.devicebridge.handler29 com.linecorp.simuse.devicebridge.handler.TreeHandler30 com.linecorp.simuse.devicebridge.server31 iOSDeviceBackend32 SimUseCore33 com.linecorp.simuse.devicebridge.service34 AndroidBackend35 SimUse36 SimUseLinux37 repository
1 Tools.Viewer.src.Details
2 Tools.Viewer.src.types
3 com.linecorp.simuse.devicebridge.config
4 com.linecorp.simuse.devicebridge.config.AuthManager
5 com.linecorp.simuse.devicebridge.handler.CaptureHandler
6 com.linecorp.simuse.devicebridge.handler.GestureHandler
7 com.linecorp.simuse.devicebridge.handler.InputHandler
8 com.linecorp.simuse.devicebridge.handler.KeyboardStateHandler
9 com.linecorp.simuse.devicebridge.handler.PasteHandler
10 com.linecorp.simuse.devicebridge.model.ElementNode
11 com.linecorp.simuse.devicebridge.server.ActionRouter
12 com.linecorp.simuse.devicebridge.server.HttpServer
13 com.linecorp.simuse.devicebridge.service.BridgeKeepAliveService
14 com.linecorp.simuse.devicebridge.service.SimuseContentProvider
15 com.linecorp.simuse.playground
16 com.linecorp.simuse.playground.MainActivity.RowAdapter
17 skills.sim-use.scripts.preflight
18 Tools.Viewer.src.Canvas2
19 com.linecorp.simuse.devicebridge.handler.InputHandler.KeyResult3
20 com.linecorp.simuse.devicebridge.handler.PasteHandler.Result4
21 com.linecorp.simuse.devicebridge.model2
22 com.linecorp.simuse.devicebridge.service.SimuseAccessibilityService1
23 com.linecorp.simuse.playground.MainActivity1
24 iOSSimBackend710205
25 skills.sim-use.scripts1
26 SimUseVideo1915
27 Tools.Viewer.src32
28 com.linecorp.simuse.devicebridge.handler11111
29 com.linecorp.simuse.devicebridge.handler.TreeHandler1
30 com.linecorp.simuse.devicebridge.server11116
31 iOSDeviceBackend1642
32 SimUseCore39
33 com.linecorp.simuse.devicebridge.service112
34 AndroidBackend17152
35 SimUse1716100
36 SimUseLinux11
37 repository31
Uses a module listed above itPart of a loopThe module itself
1 Tools.Viewer.src.Details2 Tools.Viewer.src.types3 com.linecorp.simuse.devicebridge.config4 com.linecorp.simuse.devicebridge.config.AuthManager5 com.linecorp.simuse.devicebridge.handler.CaptureHandler6 com.linecorp.simuse.devicebridge.handler.GestureHandler7 com.linecorp.simuse.devicebridge.handler.InputHandler8 com.linecorp.simuse.devicebridge.handler.KeyboardStateHandler9 com.linecorp.simuse.devicebridge.handler.PasteHandler10 com.linecorp.simuse.devicebridge.model.ElementNode11 com.linecorp.simuse.devicebridge.server.ActionRouter12 com.linecorp.simuse.devicebridge.server.HttpServer13 com.linecorp.simuse.devicebridge.service.BridgeKeepAliveService14 com.linecorp.simuse.devicebridge.service.SimuseContentProvider15 com.linecorp.simuse.playground16 com.linecorp.simuse.playground.MainActivity.RowAdapter17 skills.sim-use.scripts.preflight18 Tools.Viewer.src.Canvas19 com.linecorp.simuse.devicebridge.handler.InputHandler.KeyResult20 com.linecorp.simuse.devicebridge.handler.PasteHandler.Result21 com.linecorp.simuse.devicebridge.model22 com.linecorp.simuse.devicebridge.service.SimuseAccessibilityService23 com.linecorp.simuse.playground.MainActivity24 iOSSimBackend25 skills.sim-use.scripts26 SimUseVideo27 Tools.Viewer.src28 com.linecorp.simuse.devicebridge.handler29 com.linecorp.simuse.devicebridge.handler.TreeHandler30 com.linecorp.simuse.devicebridge.server31 iOSDeviceBackend32 SimUseCore33 com.linecorp.simuse.devicebridge.service34 AndroidBackend35 SimUse36 SimUseLinux37 repositoryTools.Viewer.src.Details1Tools.Viewer.src.types2com.linecorp.simuse.devicebridge.config3com.linecorp.simuse.devicebridge.config.AuthManager4com.linecorp.simuse.devicebridge.handler.CaptureHandler5com.linecorp.simuse.devicebridge.handler.GestureHandler6com.linecorp.simuse.devicebridge.handler.InputHandler7com.linecorp.simuse.devicebridge.handler.KeyboardStateHandler8com.linecorp.simuse.devicebridge.handler.PasteHandler9com.linecorp.simuse.devicebridge.model.ElementNode10com.linecorp.simuse.devicebridge.server.ActionRouter11com.linecorp.simuse.devicebridge.server.HttpServer12com.linecorp.simuse.devicebridge.service.BridgeKeepAliveService13com.linecorp.simuse.devicebridge.service.SimuseContentProvider14com.linecorp.simuse.playground15com.linecorp.simuse.playground.MainActivity.RowAdapter16skills.sim-use.scripts.preflight17Tools.Viewer.src.Canvas18com.linecorp.simuse.devicebridge.handler.InputHandler.KeyResult19com.linecorp.simuse.devicebridge.handler.PasteHandler.Result20com.linecorp.simuse.devicebridge.model21com.linecorp.simuse.devicebridge.service.SimuseAccessibilityService22com.linecorp.simuse.playground.MainActivity23iOSSimBackend24skills.sim-use.scripts25SimUseVideo26Tools.Viewer.src27com.linecorp.simuse.devicebridge.handler28com.linecorp.simuse.devicebridge.handler.TreeHandler29com.linecorp.simuse.devicebridge.server30iOSDeviceBackend31SimUseCore32com.linecorp.simuse.devicebridge.service33AndroidBackend34SimUse35SimUseLinux36repository372342117102051191532111111111161642391121715217161001131

At a glance — Code Health · 53% · Adequate · gated by R2, R3 ·

At a glance — Architecture · 95% · Exemplary ·

At a glance — Maturity · 91% · Exemplary ·

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

At a glance — Security · 77% · Adequate · gated by D36 ·

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
A05:2025 — Injection11High / Critical
A03:2025 — Software Supply Chain Failures5High / Critical

Roadmap

Top priorities: Resolve the 5 finding(s) in Cyclomatic Complexity; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; 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.

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

Do thisHelpsEffortDimension
Resolve the 5 finding(s) in Cyclomatic Complexity.+5.6 ptsMediumCyclomatic Complexity
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.+5.6 ptsMediumLarge Files
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.+4.7 ptsMediumSecurity & performance tooling
Bring the 50 bodies over 15 down to 15 or less in Cognitive Complexity — start with GesturePreset.validateOptions (cognitive 62), CollapsedChildrenRecovery.runProbes (cognitive 58), TapTargetingOptions.validate (cognitive 55).+4.2 ptsHighCognitive Complexity
Bring the 28 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with GesturePreset.validateOptions (cyclomatic 43), PasteboardProcess.blockingRun (cyclomatic 37), AndroidOutlineRenderer.includeNode (cyclomatic 36).+3.6 ptsHighCyclomatic Complexity
Swallowed exception (empty catch)+2.5 ptsMediumException handling
Resolve the 93 No assertions finding(s) in Test Quality — start with ForwarderInitializationGuardTests.swift (13), FrameFilterTests.swift (12), CoordinateSpaceTests.swift (7).+1.9 ptsMediumTest Quality
Add eslint as package.json scripts and run them in CI.+1.3 ptsMediumTooling

File quality

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

FileScoreBandWorst signal
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift6.0MixedExplicit Debt: TodoComment
Sources/AndroidBackend/Normalizer/TruncationHelpers.swift6.0MixedExplicit Debt: TodoComment
Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift7.0Near-cleanCyclomatic Complexity: AndroidOutlineRenderer.includeNode (cyclomatic 36)
Tests/ForwarderInitializationGuardTests.swift7.0Near-cleanTest Quality: No assertions: auditPassesParsedCommand
Tests/FrameFilterTests.swift7.0Near-cleanTest Quality: No assertions: emptyEntryComma
Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift7.0Near-cleanCyclomatic Complexity: CollapsedChildrenRecovery.runProbes (cyclomatic 29)
Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift7.0Near-cleanCyclomatic Complexity: AndroidStreamVideoCommand.streamH264 (cyclomatic 26)
Sources/SimUseCore/SelectorFrameFilter.swift7.0Near-cleanCyclomatic Complexity: SelectorFrameFilter.init (cyclomatic 22)
Sources/AndroidBackend/Normalizer/AndroidSelector.swift7.0Near-cleanCyclomatic Complexity: AndroidSelectorResolver.resolve (cyclomatic 27)
Sources/iOSSimBackend/Sim/ResizableAppSession.swift7.0Near-cleanCognitive Complexity: ResizableAppSessionMonitor.state (cognitive 18)
Tests/CoordinateSpaceTests.swift7.0Near-cleanTest Quality: No assertions: atomicUIValidates
Tests/PasteTests.swift7.1Near-cleanTest Quality: No assertions: unicodePaste
Sources/iOSSimBackend/A11y/OrientationCalibrator.swift7.1Near-cleanCyclomatic Complexity: OrientationCalibrator.calibrate (cyclomatic 24)
Tests/GestureOrientationMappingTests.swift7.1Near-cleanTest Quality: No assertions: portraitIsIdentity
Sources/SimUseCore/GesturePreset.swift7.2Near-cleanCyclomatic Complexity: GesturePreset.validateOptions (cyclomatic 43)
Sources/AndroidBackend/Bridge/BridgeClient.swift7.2Near-cleanCognitive Complexity: BridgeClient.verifiedEndpoint (cognitive 25)
Tests/IOSDeviceBackendTests.swift7.2Near-cleanTest Quality: No assertions: persistentNullRootExhaustsReadLimit
REDACTED7.2Near-cleanDependency Vulnerabilities: High CVE: REDACTED
Sources/AndroidBackend/Adb/Adb.swift7.3Near-cleanCode Duplication: Near-duplicate member family (3 members, 24 shared lines)

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

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

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

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 55 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 — 55 dimensions across the health lenses
D1D2D3D4D5D6D7D10D12D13D14D15D17D19D20D21D24D26D27D28D29D30D34D35D36D43D44AX10AX3AX4AX8AX9M1M2M3M4P1P10P2P3P6PF3R1R10R2R3R5R6R7R8R9X26X28X3X5

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, 379 of 389 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 01a1dd0a-ab78-732b-bae6-c3b9b29f0444.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`swift test --enable-code-coverage`) shows coverage is measured in your own CI.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.swift) and this repository declares a SwiftPM test suite (SimUse), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (16 contributor(s) across 458 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 15 hold 0.8% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Playgrounds/iOS/SimUsePlayground/ContentView.swift`, `Playgrounds/iOS/SimUsePlayground/Views/TouchControlView.swift`, `Sources/SimUse/Viewer/ViewerAPIHandlers.swift`, `Sources/SimUseCore/ReleaseVersion.swift`, `Sources/iOSDeviceBackend/Domain/DeviceTreeFetcher.swift`, … (+3 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • 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 dev`) 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 (bridge/app). the Android app did not build — `./gradlew :app:assembleDebug` exited -1: Tool stalled (no output) after 00:02:15.0164118.; runtime evidence skipped (launch chosen because bridge/app/build.gradle.kts applies the Android application plugin and bridge/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.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Kotlin, Python, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Kotlin, Python, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check'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.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • 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.

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.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • 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.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

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

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

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

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

28 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GesturePreset.validateOptions at 43. A further 4 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 KeyEvent.keyCodeForString at 99 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Sources/iOSSimBackend/HID/KeyCode.swift (KeyEvent.keyCodeForString at 99), Playgrounds/iOS/SimUsePlayground/Views/KeyPressView.swift (KeyCaptureUIView.getKeyInfo at 29), Playgrounds/iOS/SimUsePlayground/ContentView.swift (ContentView.destinationView 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.

GesturePreset.validateOptions (cyclomatic 43)Sources/SimUseCore/GesturePreset.swift:318
PasteboardProcess.blockingRun (cyclomatic 37)Sources/iOSSimBackend/Sim/PasteboardProcess.swift:45
AndroidOutlineRenderer.includeNode (cyclomatic 36)Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:469
TapTargetingOptions.validate (cyclomatic 33)Sources/SimUseCore/Options/TapTargetingOptions.swift:71
PasteEditMenu.presentation (cyclomatic 30)Sources/iOSSimBackend/A11y/PasteEditMenu.swift:249

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

What to do

  1. Bring the 28 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with GesturePreset.validateOptions (cyclomatic 43), PasteboardProcess.blockingRun (cyclomatic 37), AndroidOutlineRenderer.includeNode (cyclomatic 36). — 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 28 together lifts Cyclomatic Complexity from 6.9 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.4 / 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.4 / 10 · rule-coverage 100% · ceiling Prevented

50 method(s) exceeded the cognitive complexity threshold of 15; the worst was GesturePreset.validateOptions at 62.

GesturePreset.validateOptions (cognitive 62)Sources/SimUseCore/GesturePreset.swift:318
CollapsedChildrenRecovery.runProbes (cognitive 58)Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:841
TapTargetingOptions.validate (cognitive 55)Sources/SimUseCore/Options/TapTargetingOptions.swift:71
PasteboardProcess.blockingRun (cognitive 54)Sources/iOSSimBackend/Sim/PasteboardProcess.swift:45
ShellTokenizer.tokenize (cognitive 51)Sources/iOSSimBackend/Util/ShellTokenizer.swift:22

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

What to do

  1. Bring the 50 bodies over 15 down to 15 or less in Cognitive Complexity — start with GesturePreset.validateOptions (cognitive 62), CollapsedChildrenRecovery.runProbes (cognitive 58), TapTargetingOptions.validate (cognitive 55). — 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 50 together lifts Cognitive Complexity from 6.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes9.4 / 10Stronggated by 7 serious findings✓ 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 9.4 / 10 · rule-coverage 100% · ceiling Prevented

7 god class(es) detected.

MethodTooLong: IOSSimTapCommand.performTap · ×3Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift:163
FileTooLong: A11y/AccessibilityFetcher.swift · ×2Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift
ClassTooLong: AndroidOutlineRendererSources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:10
TooManyMethods: BridgeClientSources/AndroidBackend/Bridge/BridgeClient.swift:29

What to do

  1. Resolve the 3 MethodTooLong finding(s) in God Classes — start with IOSSimTapCommand.swift, GesturePresetsView.swift, AndroidOutlineRenderer.swift. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 FileTooLong finding(s) in God Classes — start with AccessibilityFetcher.swift, AndroidOutlineRenderer.swift. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 ClassTooLong finding(s) in God Classes — start with AndroidOutlineRenderer.swift. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication7.3 / 10Strong✓ 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 7.3 / 10 · rule-coverage 100% · ceiling Verified

46 duplicated block group(s) detected. 6.8 % of the production lines (2,788 of 41,236) are in a reported copy. A further 76 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Edited copy of a member (9 corresponding lines) · ×8Sources/SimUseVideo/H264MuxingPipeline.swift:49
Edited copy of a member (13 corresponding lines) · ×5Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:1126
Edited copy of a member (8 corresponding lines) · ×5Sources/AndroidBackend/Bridge/BridgeClient.swift:279
Edited copy of a member (6 corresponding lines) · ×5Sources/SimUseCore/JSONEnvelopeWriter.swift:100
Edited copy of a member (29 corresponding lines) · ×4Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:1047

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

What to do

  1. Resolve the 8 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with H264MuxingPipeline.swift, IOSSimBatchCommand.swift, GestureHandler.kt. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 5 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with AccessibilityFetcher.swift, AndroidSelector.swift, SelectorTextMatcher.swift. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 5 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with BridgeClient.swift, DaemonCommand.swift, AndroidSwipeCommand.swift. — One of this dimension's main actionable groups (5 warning-level).

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

D5 · Coupling9.4 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

13 production modules (Gradle+npm+SwiftPM+XcodeGen), 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; an XcodeGen target's dependency on a local Swift package or on a target of another project is not visible there; 1 module(s) off the main sequence, with abstractness counted on 11 of the 13 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: SimUseCore

What to do

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

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

D6 · Cohesion (LCOM4)9.5 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

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

1 of 23 classes have LCOM4 above 3.

Low cohesion: KeyCaptureUIView (LCOM4 5)Playgrounds/iOS/SimUsePlayground/Views/KeyPressView.swift:140

What to do

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

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

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Detailed fixes: d7_recommendation.md.

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

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

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

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

2 skipped (2 with a documented reason), 93 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1827 tests.

No assertions: relWithoutScreenFrame · ×93Tests/AccessibilityTargetResolverTests.swift:413
Skipped (documented): swipeFromLeftEdge · ×2Tests/GestureTests.swift:75

What to do

  1. Resolve the 93 No assertions finding(s) in Test Quality — start with ForwarderInitializationGuardTests.swift (13), FrameFilterTests.swift (12), CoordinateSpaceTests.swift (7). — One of this dimension's main actionable groups (93 warning-level).

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

D12 · Dependency Hygiene9.9 / 10Exemplary✓ Tool-verified

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

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

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

1 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.

Outdated: swift-argument-parser

✓ On the Gold path — maintain.

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ 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 3 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 4 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 2 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 Swift Package.swift/Package.resolved, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

Top hotspots: Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift (8×26=208); Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift (6×25=150); Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift (5×30=150) Repeated repair below the complexity floor: Sources/AndroidBackend/Bridge/BridgeClient.swift (9 of 11 changes were fixes); Sources/iOSDeviceBackend/Verbs/IOSDeviceCommand.swift (6 of 11 changes were fixes); skills/sim-use/scripts/preflight.py (6 of 7 changes were fixes)

Repeated repair: Sources/AndroidBackend/Bridge/BridgeClient.swift · ×18Sources/AndroidBackend/Bridge/BridgeClient.swift:521
Hotspot: Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift · ×7Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:192

What to do

  1. Resolve the 18 Repeated repair finding(s) in Churn × Complexity Hotspots — start with BridgeClient.swift, IOSDeviceCommand.swift, preflight.py. — One of this dimension's main actionable groups (18 warning-level).
  2. Resolve the 7 Hotspot finding(s) in Churn × Complexity Hotspots — start with AndroidStreamVideoCommand.swift, IOSSimPasteCommand.swift, IOSSimTapCommand.swift. — One of this dimension's main actionable groups (7 warning-level).

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

D17 · Explicit Debt10.0 / 10Stronggated by 3 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

3 deducted task-comment markers across 41236 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 · ×3Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:480

What to do

  1. Resolve the 3 TodoComment finding(s) in Explicit Debt — start with AndroidRecordVideoCommand.swift (2), TruncationHelpers.swift. — One of this dimension's main actionable groups (3 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality10.0 / 10Exemplary○ Nothing flagged

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

0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

✓ On the Gold path — maintain.

Detailed fixes: d20_recommendation.md.

D21 · Naming Consistency6.1 / 10Adequate✓ Tool-verified

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

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

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

2 naming inconsistencies among 51 declarations measured against a convention their peers follow.

`resolveOnPATH` spells `PATH` where 35 names in the project spell it `Path`Sources/AndroidBackend/Adb/Adb.swift:286
`iosHidButton` spells `Hid` where 14 names in the project spell it `HID`Sources/iOSSimBackend/Verbs/IOSSimButtonCommand.swift:33

What to do

  1. Resolve the 1 `resolveOnPATH` spells `PATH` where 35 names in the project spell it… finding(s) in Naming Consistency — start with Adb.swift. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `iosHidButton` spells `Hid` where 14 names in the project spell it `HID` finding(s) in Naming Consistency — start with IOSSimButtonCommand.swift. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value10.0 / 10Exemplary○ Nothing flagged

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

0 of 34 judged comments only repeat the code they sit on (0.0 %).

✓ On the Gold path — maintain.

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

1 of 5 build units (Gradle, SwiftPM, XcodeGen, npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

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

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

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

36 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.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)8.4 / 10Adequategated by 11 critical findings✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

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

11 finding(s): 0 critical, 11 high, 0 medium, 0 low. 10 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `Playgrounds/Android/gradlew` (line 74, line 178), `bridge/gradlew` (line 74, line 178), `scripts/build.sh` (line 126), `scripts/e2e-matrix.sh` — 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.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

  1. Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D34 · Knowledge Freshness9.8 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

3 of 196 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Sources/SimUseVideo/AnnexBStreamParser.swift. Counted over 196 of the 244 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×3Sources/SimUseVideo/AnnexBStreamParser.swift:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 10 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.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

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

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

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

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

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

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

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

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

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

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 documentation8.0 / 10Strong✓ 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.

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 · Observability8.0 / 10Strong✓ Tool-verified

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

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

P3 · Security & performance 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 1 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:21
  • `Tools/Viewer/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`. — Tools/Viewer/package.json:12

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.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

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 Safety10.0 / 10Exemplary✓ 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.

R10 · Code Duplication10.0 / 10Exemplary✓ 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.

R2 · Cyclomatic Complexity2.0 / 10Critical✓ 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.

  • onKey has cyclomatic complexity 20 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — Tools/Viewer/src/App.tsx:158
  • App has cyclomatic complexity 17 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. — Tools/Viewer/src/App.tsx:6
  • (anonymous) has cyclomatic complexity 14 and cognitive complexity 21; 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. — Tools/Viewer/src/App.tsx:136
  • ElementBox 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. — Tools/Viewer/src/Canvas.tsx:240
  • Details 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. — Tools/Viewer/src/Details.tsx:23
R3 · Large Files2.0 / 10Critical✓ 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.

  • Tools/Viewer/src/Canvas.tsx has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — Tools/Viewer/src/Canvas.tsx:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R5 · Dependency Freshness9.8 / 10Exemplary✓ Tool-verified

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

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

R6 · Tooling6.7 / 10Strong✓ 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.

  • test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add eslint as package.json scripts and run them in CI.
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified

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

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

R8 · Dependency Hygiene10.0 / 10Exemplary✓ 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.

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

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

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

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.

X3 · Exception handling5.8 / 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. (×11) — bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:233, bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:240, bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:248, …
  • `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. — bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/PasteHandler.kt:65
  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — Sources/iOSSimBackend/Sim/XcodeCompatibility.swift:66, Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:909

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types9.9 / 10Exemplary✓ Tool-verified

Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.

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

Reference — by lens

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

LensScoreRatingImpact
Code Health53%Adequate — gated by R2, R3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture95%ExemplarySolid.
Maturity91%ExemplarySolid.
Readiness63%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security77%Adequate — gated by D36Capped 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.

  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for

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

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

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

  • AC1 Text alternatives — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC2 Forms & labels — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC3 Page structure — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — The only markup in this repository is in its own developer tools (a root `tools/` or `scripts/` tree), which is not the product's UI — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: 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 Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — no exported interface declares behaviour
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • 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: Tool stalled (no output) after 00:02:15.0164118.; runtime evidence skipped (launch chosen because bridge/app/build.gradle.kts applies the Android application plugin and bridge/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.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D11 Test Reliability — Test reliability not included — the .swift suite was found but not re-run
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D8 Code Coverage — Coverage not measured — Swift suite
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (9 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
  • 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
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, Python, Swift source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `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.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R4 Test Coverage — no production JavaScript/TypeScript files to cover (0 test file(s) present) — nothing to measure
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X12 Unreachable branch — X12 reached only 9% of this repository's production lines — swift (37,645 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — X16 reached only 8% of this repository's production lines — swift (37,645 lines), python (234 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — X18 reached only 8% of this repository's production lines — swift (37,645 lines), python (234 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — X21 reached only 9% of this repository's production lines — swift (37,645 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — X27 reached only 6% of this repository's production lines — swift (37,645 lines), typescript (1,051 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.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 — 12 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
Serious — 352 finding(s)
D10 · Test Quality · No assertions · ×93
  • No assertions: relWithoutScreenFrame Tests/AccessibilityTargetResolverTests.swift:413 — 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: emptyInputRejected Tests/BatchPasteStepTests.swift:103 — 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: fileInputSource Tests/BatchTests.swift:25 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: androidButtonPerformContract Tests/ButtonForwarderTests.swift:44 — 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: homeButtonPress Tests/ButtonTests.swift:7 — 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: lockButtonPress Tests/ButtonTests.swift:19 — 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: sideButtonPress Tests/ButtonTests.swift:28 — 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: atomicUIValidates Tests/CoordinateSpaceTests.swift:66 — 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: splitUIValidates Tests/CoordinateSpaceTests.swift:73 — 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: splitNativeStillValidates Tests/CoordinateSpaceTests.swift:80 — 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: explicitPointUIValidates Tests/CoordinateSpaceTests.swift:113 — 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: selectorValidates Tests/CoordinateSpaceTests.swift:132 — 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: androidMultiTouchGestureParseFlag Tests/CoordinateSpaceTests.swift:341 — 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: coordinateTarget Tests/CoordinateSpaceTests.swift:372 — 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: idleTimerDefersWhileRequestInFlight Tests/DaemonServerIdleTimerTests.swift:152 — 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: clearsHIDCache Tests/DaemonStaleSimulatorTests.swift:107 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: androidDescribePerformContract Tests/DescribeUIForwarderTests.swift:89 — 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: mainProceeds Tests/DisplayRoutingTests.swift:378 — 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: auditPassesParsedCommand Tests/ForwarderInitializationGuardTests.swift:134 — 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: paste Tests/ForwarderInitializationGuardTests.swift:139 — 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: screenshot Tests/ForwarderInitializationGuardTests.swift:144 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, 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: swipe Tests/ForwarderInitializationGuardTests.swift:149 — 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: type Tests/ForwarderInitializationGuardTests.swift:156 — 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: recordVideo Tests/ForwarderInitializationGuardTests.swift:161 — 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: streamVideo Tests/ForwarderInitializationGuardTests.swift:166 — 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.
  • + 68 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Repeated repair · ×18
  • Repeated repair: Sources/AndroidBackend/Bridge/BridgeClient.swift Sources/AndroidBackend/Bridge/BridgeClient.swift:521 — Sources/AndroidBackend/Bridge/BridgeClient.swift changed 11 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is BridgeClient.sendRaw at line 521), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(android): serialize shared bridge session transitions”; “fix(android): reuse recent bridge sessions and recover from other listeners”; “fix(android): cache bridge discovery outside HTTP transport”; “fix(android): discover and recover fallback bridge endpoints”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/AndroidBackend/Bridge/BridgeClient.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/iOSDeviceBackend/Verbs/IOSDeviceCommand.swift Sources/iOSDeviceBackend/Verbs/IOSDeviceCommand.swift:441 — Sources/iOSDeviceBackend/Verbs/IOSDeviceCommand.swift changed 11 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is Tap.validate at line 441), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: keep max-length and slash-containing names inside the output contract”; “fix: never remove the existing screenshot before capture succeeds”; “fix: stop a rejected non-PNG screenshot path from deleting the target”; “fix: align ios-device selector matching with the shared simulator/Android policy”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSDeviceBackend/Verbs/IOSDeviceCommand.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: skills/sim-use/scripts/preflight.py skills/sim-use/scripts/preflight.py:119 — skills/sim-use/scripts/preflight.py changed 7 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is preflight.check_device_listed at line 119), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: close the resize-session guard gaps found in review”; “fix: limit the empty-outline exclusion to physical iOS”; “fix: also warn on an empty outline in skill preflight”; “fix: surface remote content recovery in skill preflight”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- skills/sim-use/scripts/preflight.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.
  • Repeated repair: Sources/AndroidBackend/Bridge/BridgeSession.swift Sources/AndroidBackend/Bridge/BridgeSession.swift:57 — Sources/AndroidBackend/Bridge/BridgeSession.swift changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is BridgeSessionStore.withExclusiveAccess at line 57), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(android): accept IPv6 serials in bridge session paths”; “fix(android): serialize shared bridge session transitions”; “fix(android): reuse recent bridge sessions and recover from other listeners”; “fix(android): cache bridge discovery outside HTTP transport”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/AndroidBackend/Bridge/BridgeSession.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/iOSSimBackend/Verbs/IOSSimBatchCommand.swift Sources/iOSSimBackend/Verbs/IOSSimBatchCommand.swift:191 — Sources/iOSSimBackend/Verbs/IOSSimBatchCommand.swift changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is IOSSimBatchCommand.execute at line 191), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ios): prevent unsafe paste retries and menu targets”; “fix(ios): restore verified simulator paste”; “fix: forward caller-side stdin and file input to the daemon inline”; “fix: close the resize-session guard gaps found in review”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/Verbs/IOSSimBatchCommand.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/SimUseVideo/MPEGTSStreamWriter.swift Sources/SimUseVideo/MPEGTSStreamWriter.swift:136 — Sources/SimUseVideo/MPEGTSStreamWriter.swift changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is MPEGTSStreamWriter.annexB at line 136), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: keep the stream cancellable, and declare the timeline discontinuity”; “fix: make the transport stream conformant, not just ffplay-compatible”; “fix: keep the preview timeline compact across idle periods”; “fix: keep the MPEG-TS clock advancing, and document a command that works”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/SimUseVideo/MPEGTSStreamWriter.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/iOSSimBackend/Sim/RoutingDisplay.swift Sources/iOSSimBackend/Sim/RoutingDisplay.swift:332 — Sources/iOSSimBackend/Sim/RoutingDisplay.swift changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is RoutingDisplayGuard.captureMovedNotice at line 332), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ios): crop to the actual scene, pack BGRA rows, check fresh state (S5-001..003)”; “fix(ios): say "resized", not "moved", when a session scene changes size mid-capture”; “fix(ios): keep routing in step with the tree and with reboots”; “fix(ios): re-read the display topology when the AX root changes size”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/Sim/RoutingDisplay.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/SimUse/Viewer/ViewerAPIHandlers.swift Sources/SimUse/Viewer/ViewerAPIHandlers.swift:292 — Sources/SimUse/Viewer/ViewerAPIHandlers.swift changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ViewerAPIHandlers.parseAppLine at line 292), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(viewer): record a reader callback's bytes before finish() returns (S6-002)”; “fix: read a viewer subprocess's last output; make two load-sensitive tests deterministic”; “fix: address round-1 review findings on physical-device routing”; “fix: keep physical iOS rows out of the Viewer, which cannot drive them”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/SimUse/Viewer/ViewerAPIHandlers.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/AndroidBackend/Verbs/AndroidDeviceController.swift Sources/AndroidBackend/Verbs/AndroidDeviceController.swift:59 — Sources/AndroidBackend/Verbs/AndroidDeviceController.swift changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is AndroidDeviceController.describeUI at line 59), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(android): reuse recent bridge sessions and recover from other listeners”; “fix(android): discover and recover fallback bridge endpoints”; “fix: remove forwards by serial and report the bridge host”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/AndroidBackend/Verbs/AndroidDeviceController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/SimUseCore/Daemon/DaemonDispatch.swift Sources/SimUseCore/Daemon/DaemonDispatch.swift:140 — Sources/SimUseCore/Daemon/DaemonDispatch.swift changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is DaemonDispatch.handle at line 140), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ios): prevent unsafe paste retries and menu targets”; “fix: refuse daemon requests from another connection”; “fix: scope remote adb sessions to their adb server”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/SimUseCore/Daemon/DaemonDispatch.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/SimUse/Commands/Paste.swift Sources/SimUse/Commands/Paste.swift:102 — Sources/SimUse/Commands/Paste.swift changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is Paste.execute at line 102), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ios): restore verified simulator paste”; “fix: forward caller-side stdin and file input to the daemon inline”; “fix: address round-1 review findings on physical-device routing”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/SimUse/Commands/Paste.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift:66 — Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is IOSSimScreenshotCommand.execute at line 66), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: detect Xcode 27 resizable app sessions and refuse undeliverable touch input”; “fix: sanitise user-editable names in default screenshot filenames”; “fix: stop a rejected non-PNG screenshot path from deleting the target”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/SimUseVideo/MPEGTSMuxer.swift Sources/SimUseVideo/MPEGTSMuxer.swift:190 — Sources/SimUseVideo/MPEGTSMuxer.swift changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is MPEGTSMuxer.adaptationField at line 190), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: keep the stream cancellable, and declare the timeline discontinuity”; “fix: make the transport stream conformant, not just ffplay-compatible”; “fix: keep the MPEG-TS clock advancing, and document a command that works”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/SimUseVideo/MPEGTSMuxer.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift:37 — Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is IOSSimTapCommand.toBatchPrimitives at line 37), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ios): restore verified simulator paste”; “fix(ios): check the scene size before a snapshot calibration; two-finger batch gestures”; “fix(tap): honor --coordinate-space for explicit coordinates”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/iOSDeviceBackend/AXAudit/AXAuditClient.swift Sources/iOSDeviceBackend/AXAudit/AXAuditClient.swift:117 — Sources/iOSDeviceBackend/AXAudit/AXAuditClient.swift changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is AXAuditClient.rootElement at line 117), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: retry transient missing physical-device accessibility roots”; “fix: surface nav-bar back button and identifiers in ios-device ui”; “fix: harden experimental physical iOS device support”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSDeviceBackend/AXAudit/AXAuditClient.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/iOSDeviceBackend/Domain/DeviceOutline.swift Sources/iOSDeviceBackend/Domain/DeviceOutline.swift:23 — Sources/iOSDeviceBackend/Domain/DeviceOutline.swift changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is DeviceOutline.init at line 23), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: align ios-device selector matching with the shared simulator/Android policy”; “fix: surface nav-bar back button and identifiers in ios-device ui”; “fix: harden experimental physical iOS device support”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSDeviceBackend/Domain/DeviceOutline.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/AndroidBackend/Adb/Adb.swift Sources/AndroidBackend/Adb/Adb.swift:178 — Sources/AndroidBackend/Adb/Adb.swift changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is Adb.run at line 178), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: remove forwards by serial and report the bridge host”; “fix: scope remote adb sessions to their adb server”; “fix: report a missing adb binary as adbMissing on Linux”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/AndroidBackend/Adb/Adb.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: Sources/SimUseCore/OutputFilePath.swift Sources/SimUseCore/OutputFilePath.swift:21 — Sources/SimUseCore/OutputFilePath.swift changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is OutputFilePath.resolve at line 21), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: keep max-length and slash-containing names inside the output contract”; “fix: never remove the existing screenshot before capture succeeds”; “fix: stop a rejected non-PNG screenshot path from deleting the target”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/SimUseCore/OutputFilePath.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
X3 · Exception handling · Swallowed exception (empty catch) · ×11
  • Swallowed exception (empty catch) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:233 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:240 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:248 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:359 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:413 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/HttpServer.kt:79 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/HttpServer.kt:126 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/HttpServer.kt:218 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/InputHandler.kt:62 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/KeyboardStateHandler.kt:30 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/PasteHandler.kt:87 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×8
  • Edited copy of a member (9 corresponding lines) Sources/SimUseVideo/H264MuxingPipeline.swift:49 — Sources/SimUseVideo/H264MuxingPipeline.swift:49-57 | Sources/SimUseVideo/H264MuxingPipeline.swift:69-84 — 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) Sources/iOSSimBackend/Verbs/IOSSimBatchCommand.swift:97 — Sources/iOSSimBackend/Verbs/IOSSimBatchCommand.swift:97-122 | Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:102-110 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/GestureHandler.kt:21 — bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/GestureHandler.kt:21-29 | bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/GestureHandler.kt:38-47 — 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) Sources/AndroidBackend/Verbs/AndroidPasteCommand.swift:66 — Sources/AndroidBackend/Verbs/AndroidPasteCommand.swift:66-78 | Sources/AndroidBackend/Verbs/AndroidTypeCommand.swift:61-69 — 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) Sources/SimUse/Commands/Swipe.swift:62 — Sources/SimUse/Commands/Swipe.swift:62-70 | Sources/iOSSimBackend/Verbs/IOSSimSwipeCommand.swift:74-82 — 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) Sources/SimUse/Commands/Touch.swift:89 — Sources/SimUse/Commands/Touch.swift:89-97 | Sources/iOSSimBackend/Verbs/IOSSimTouchCommand.swift:81-89 — 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) Sources/SimUse/Commands/DescribeUI.swift:93 — Sources/SimUse/Commands/DescribeUI.swift:93-101 | Sources/iOSSimBackend/Verbs/IOSSimDescribeUICommand.swift:181-189 — 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) Sources/SimUse/Commands/MultiTouch.swift:115 — Sources/SimUse/Commands/MultiTouch.swift:115-123 | Sources/iOSSimBackend/Verbs/IOSSimMultiTouchCommand.swift:125-133 — 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×7
  • Hotspot: Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:192 — Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in AndroidStreamVideoCommand.streamH264 at line 192. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift:136 — Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in IOSSimPasteCommand.validateOptions at line 136. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift:163 — Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in IOSSimTapCommand.performTap at line 163. 2 of those changes were fix/bug commits, 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-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Sources/iOSSimBackend/Normalizer/OutlineSideBars.swift Sources/iOSSimBackend/Normalizer/OutlineSideBars.swift:82 — Sources/iOSSimBackend/Normalizer/OutlineSideBars.swift changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in OutlineSideBars.bar at line 82. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/Normalizer/OutlineSideBars.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Sources/iOSSimBackend/A11y/OrientationCalibrator.swift Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:161 — Sources/iOSSimBackend/A11y/OrientationCalibrator.swift changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in OrientationCalibrator.calibrate at line 161. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/A11y/OrientationCalibrator.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Sources/SimUseCore/Options/TapTargetingOptions.swift Sources/SimUseCore/Options/TapTargetingOptions.swift:71 — Sources/SimUseCore/Options/TapTargetingOptions.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in TapTargetingOptions.validate at line 71. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/SimUseCore/Options/TapTargetingOptions.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:75 — Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in OutlineFormatter.render at line 75. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 16:06:16 +09:00' --until='2026-11-12 16:06:16 +09:00' --full-history --no-merges -- Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×5
  • Edited copy of a member (13 corresponding lines) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:1126 — Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:1126-1142 | Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:723-735 — 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) Sources/AndroidBackend/Normalizer/AndroidSelector.swift:149 — Sources/AndroidBackend/Normalizer/AndroidSelector.swift:149-163 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:103-115 — 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) Sources/SimUseCore/SelectorTextMatcher.swift:46 — Sources/SimUseCore/SelectorTextMatcher.swift:46-58 | Sources/SimUseCore/SelectorTextMatcher.swift:65-79 — 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) Sources/SimUseVideo/VideoRecordingOptions.swift:12 — Sources/SimUseVideo/VideoRecordingOptions.swift:12-24 | Sources/SimUseVideo/VideoRecordingOptions.swift:29-41 — 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) Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift:80 — Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift:80-94 | Sources/iOSSimBackend/Verbs/IOSSimKeyCommand.swift:77-89 — 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 (8 corresponding lines) · ×5
  • Edited copy of a member (8 corresponding lines) Sources/AndroidBackend/Bridge/BridgeClient.swift:279 — Sources/AndroidBackend/Bridge/BridgeClient.swift:279-286 | Sources/AndroidBackend/Bridge/BridgeClient.swift:325-339 — 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) Sources/SimUseCore/Daemon/DaemonCommand.swift:145 — Sources/SimUseCore/Daemon/DaemonCommand.swift:145-152 | Sources/SimUseCore/Device.swift:122-130 — 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) Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift:115 — Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift:115-122 | Sources/AndroidBackend/Verbs/AndroidTapCommand.swift:132-144 — 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) Sources/SimUseVideo/H264PassthroughRecorder.swift:127 — Sources/SimUseVideo/H264PassthroughRecorder.swift:127-134 | Sources/SimUseVideo/VideoCommandSupport.swift:293-300 — 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) Sources/iOSSimBackend/Sim/DevicePosture.swift:244 — Sources/iOSSimBackend/Sim/DevicePosture.swift:244-251 | Sources/iOSSimBackend/Sim/PostureController.swift:280-287 — 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 · Edited copy of a member (6 corresponding lines) · ×5
  • Edited copy of a member (6 corresponding lines) Sources/SimUseCore/JSONEnvelopeWriter.swift:100 — Sources/SimUseCore/JSONEnvelopeWriter.swift:100-106 | Sources/SimUseCore/JSONEnvelopeWriter.swift:116-121 — 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) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:311 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:311-316 | Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:318-323 — 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) Sources/SimUseCore/GesturePreset.swift:79 — Sources/SimUseCore/GesturePreset.swift:79-85 | Sources/SimUseCore/SwipeCoordinates.swift:39-44 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) Sources/AndroidBackend/Bridge/ElementNode.swift:60 — Sources/AndroidBackend/Bridge/ElementNode.swift:60-65 | Sources/SimUseCore/Outline.swift:262-267 — 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) Sources/SimUse/Viewer/ViewerAPIHandlers.swift:400 — Sources/SimUse/Viewer/ViewerAPIHandlers.swift:400-405 | Sources/SimUseCore/DaemonPaths.swift:169-174 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×4
  • Edited copy of a member (29 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:1047 — Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:1047-1082 | Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:530-558 — 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) Sources/iOSSimBackend/Sim/ResizableAppSession.swift:229 — Sources/iOSSimBackend/Sim/ResizableAppSession.swift:229-267 | Sources/iOSSimBackend/Sim/SimulatorDisplayTopology.swift:323-351 — 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) Sources/iOSSimBackend/Verbs/IOSSimButtonCommand.swift:137 — Sources/iOSSimBackend/Verbs/IOSSimButtonCommand.swift:137-166 | Sources/iOSSimBackend/Verbs/IOSSimKeyCommand.swift:91-119 — 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) Sources/iOSSimBackend/Verbs/IOSSimKeyComboCommand.swift:95 — Sources/iOSSimBackend/Verbs/IOSSimKeyComboCommand.swift:95-126 | Sources/iOSSimBackend/Verbs/IOSSimKeySequenceCommand.swift:87-115 — 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 (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidSelector.swift:196 — Sources/AndroidBackend/Normalizer/AndroidSelector.swift:196-204 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:134-140 — 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) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:313 — bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:313-319 | bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:332-339 — 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) Sources/iOSDeviceBackend/Domain/DeviceTreeFetcher.swift:13 — Sources/iOSDeviceBackend/Domain/DeviceTreeFetcher.swift:13-29 | Sources/iOSDeviceBackend/AXAudit/AXAuditElement.swift:67-73 — 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) Sources/SimUseCore/Daemon/DaemonProtocol.swift:176 — Sources/SimUseCore/Daemon/DaemonProtocol.swift:176-183 | Sources/SimUseCore/Daemon/DaemonDispatch.swift:44-50 — 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 copy of a member (4 corresponding lines) · ×4
  • Edited copy of a member (4 corresponding lines) Sources/AndroidBackend/Normalizer/TruncationHelpers.swift:31 — Sources/AndroidBackend/Normalizer/TruncationHelpers.swift:31-34 | Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:562-565 — 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) Sources/SimUseCore/SelectorFrameFilter.swift:45 — Sources/SimUseCore/SelectorFrameFilter.swift:45-48 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:171-174 — 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) Sources/AndroidBackend/Verbs/AndroidTouchCommand.swift:71 — Sources/AndroidBackend/Verbs/AndroidTouchCommand.swift:71-74 | Sources/SimUse/Commands/Touch.swift:136-145 — 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) Sources/AndroidBackend/Verbs/AndroidAppStateCommand.swift:38 — Sources/AndroidBackend/Verbs/AndroidAppStateCommand.swift:38-41 | Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift:40-43 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×4
  • Edited copy of a member (3 corresponding lines) Sources/AndroidBackend/Bridge/BridgeSession.swift:138 — Sources/AndroidBackend/Bridge/BridgeSession.swift:138-141 | Sources/SimUseCore/OutlineCache.swift:203-205 — 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) Sources/AndroidBackend/Bridge/BridgeSession.swift:98 — Sources/AndroidBackend/Bridge/BridgeSession.swift:98-100 | Sources/SimUseCore/OutlineCache.swift:94-96 — 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) Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift:98 — Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift:98-100 | Sources/iOSSimBackend/Verbs/IOSSimTypeCommand.swift:69-71 — 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) Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift:75 — Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift:75-77 | Sources/AndroidBackend/Verbs/AndroidPingCommand.swift:46-48 — 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 (9 lines × 2) · ×4
  • Duplicated block (9 lines × 2) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:223 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:223-231 | Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:181-189 — before extracting anything, compare `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift` and `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
  • Duplicated block (9 lines × 2) Sources/iOSSimBackend/HID/VendorDefinedHID.swift:101 — Sources/iOSSimBackend/HID/VendorDefinedHID.swift:101-109 | Sources/iOSSimBackend/HID/VendorDefinedHID.swift:121-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 `Sources/iOSSimBackend/HID/VendorDefinedHID.swift:101` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Sources/iOSSimBackend/Normalizer/ListDetector.swift:267 — Sources/iOSSimBackend/Normalizer/ListDetector.swift:267-275 | Sources/iOSSimBackend/Normalizer/ListDetector.swift:390-398 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/iOSSimBackend/Normalizer/ListDetector.swift:267` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) Sources/iOSSimBackend/Sim/ResizableAppSession.swift:77 — Sources/iOSSimBackend/Sim/ResizableAppSession.swift:77-85 | Sources/iOSSimBackend/Sim/SimulatorDisplayTopology.swift:166-174 — 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 (6 lines × 2) · ×4
  • Duplicated block (6 lines × 2) Sources/AndroidBackend/Normalizer/AndroidListDetector.swift:159 — Sources/AndroidBackend/Normalizer/AndroidListDetector.swift:159-164 | Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:810-815 — 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) Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift:59 — Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift:59-64 | Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift:137-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (6 lines × 2) Sources/SimUse/Commands/LongPress.swift:71 — Sources/SimUse/Commands/LongPress.swift:71-76 | Sources/SimUse/Commands/Tap.swift:107-112 — 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) Sources/SimUse/Commands/RecordVideo.swift:57 — Sources/SimUse/Commands/RecordVideo.swift:57-62 | Sources/SimUse/Commands/Screenshot.swift:44-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/SimUse/Commands/RecordVideo.swift:64` calls `validate` and `Sources/SimUse/Commands/Screenshot.swift:51` 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.
D17 · Explicit Debt · TodoComment · ×3
  • TodoComment Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:480 — /// TODO(persistent-screencap-pipe): if frame budget tightens (e.g. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:485 — /// TODO is the cheaper performance lever to reach for first when — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment Sources/AndroidBackend/Normalizer/TruncationHelpers.swift:11 — /// TODO(width-aware-truncation): Truncates by grapheme-cluster — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D3 · God Classes · MethodTooLong · ×3
  • MethodTooLong: IOSSimTapCommand.performTap Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift:163 — MethodTooLong — performTap runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× 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: GesturePresetsView.body Playgrounds/iOS/SimUsePlayground/Views/GesturePresetsView.swift:111 — MethodTooLong — body runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: AndroidOutlineRenderer.render Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:57 — MethodTooLong — render 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.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Sources/SimUse/Commands/Button.swift:60 — Sources/SimUse/Commands/Button.swift:60-73 | Sources/SimUse/Commands/LongPress.swift:78-91 | Sources/SimUse/Commands/Paste.swift:102-115 | Sources/SimUse/Commands/Touch.swift:99-112 | Sources/SimUse/Commands/Type.swift:79-92 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Sources/SimUse/Commands/Gesture.swift:132 — Sources/SimUse/Commands/Gesture.swift:132-145 | Sources/SimUse/Commands/MultiTouch.swift:125-138 | Sources/SimUse/Commands/RecordVideo.swift:68-81 | Sources/SimUse/Commands/StreamVideo.swift:100-113 | Sources/SimUse/Commands/Swipe.swift:76-89 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Sources/iOSSimBackend/Verbs/IOSSimFoldCommand.swift:83 — Sources/iOSSimBackend/Verbs/IOSSimFoldCommand.swift:83-89 | Sources/iOSSimBackend/Verbs/IOSSimKeyComboCommand.swift:58-66 | Sources/iOSSimBackend/Verbs/IOSSimKeyCommand.swift:54-65 | Sources/iOSSimBackend/Verbs/IOSSimKeySequenceCommand.swift:45-53 | Sources/iOSSimBackend/Verbs/IOSSimRotateCommand.swift:59-65 — 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 (5 corresponding lines) · ×3
  • Edited copy of a member (5 corresponding lines) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:327 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:327-331 | Sources/SimUseVideo/VideoCommandSupport.swift:81-87 — 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) Sources/iOSSimBackend/A11y/DisplayOrientation.swift:180 — Sources/iOSSimBackend/A11y/DisplayOrientation.swift:180-184 | Sources/iOSSimBackend/A11y/DisplayOrientation.swift:186-190 — 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) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:45 — Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:45-50 | Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:66-70 — 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 · Duplicated block (17 lines × 2) · ×3
  • Duplicated block (17 lines × 2) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:163 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:163-179 | Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:144-160 — before extracting anything, compare `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift` and `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:163` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (17 lines × 2) Sources/SimUse/Commands/Gesture.swift:114 — Sources/SimUse/Commands/Gesture.swift:114-130 | Sources/iOSSimBackend/Verbs/IOSSimGestureCommand.swift:112-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SimUse/Commands/Gesture.swift:114` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (17 lines × 2) Sources/SimUseCore/GesturePreset.swift:318 — Sources/SimUseCore/GesturePreset.swift:318-334 | Sources/iOSSimBackend/Verbs/IOSSimGestureCommand.swift:134-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SimUseCore/GesturePreset.swift:318` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×3
  • Duplicated block (16 lines × 2) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:265 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:265-280 | Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:288-303 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:265` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:390 — Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:390-405 | Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:251-266 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:390` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) Sources/iOSSimBackend/Normalizer/ListDetector.swift:278 — Sources/iOSSimBackend/Normalizer/ListDetector.swift:278-293 | Sources/iOSSimBackend/Normalizer/ListDetector.swift:401-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/iOSSimBackend/Normalizer/ListDetector.swift:278` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/iOSSimBackend/Normalizer/ListDetector.swift:276` calls `Double` and `Sources/iOSSimBackend/Normalizer/ListDetector.swift:400` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift:142 — Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift:142-154 | Sources/AndroidBackend/Verbs/AndroidTapCommand.swift:197-209 — 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 (13 lines × 2) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:403 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:403-415 | Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:244-256 — before extracting anything, compare `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift` and `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
  • Duplicated block (13 lines × 2) Sources/SimUseCore/SelectorFrameFilter.swift:124 — Sources/SimUseCore/SelectorFrameFilter.swift:124-136 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:242-254 — before extracting anything, compare `Sources/SimUseCore/SelectorFrameFilter.swift` and `Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SimUseCore/SelectorFrameFilter.swift:124` 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 (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) Sources/SimUseVideo/MPEGTSMuxer.swift:273 — Sources/SimUseVideo/MPEGTSMuxer.swift:273-283 | Sources/SimUseVideo/MPEGTSMuxer.swift:294-303 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2) Sources/iOSSimBackend/Sim/ResizableAppSession.swift:230 — Sources/iOSSimBackend/Sim/ResizableAppSession.swift:230-239 | Sources/iOSSimBackend/Sim/SimulatorDisplayTopology.swift:324-333 — 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 (10 lines × 2) Sources/SimUse/Commands/DescribeUI.swift:103 — Sources/SimUse/Commands/DescribeUI.swift:103-112 | Sources/SimUse/Commands/Tap.swift:114-127 — 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 (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) Sources/SimUse/Commands/Type.swift:114 — Sources/SimUse/Commands/Type.swift:114-121 | Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift:336-343 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SimUse/Commands/Type.swift:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) Sources/SimUse/Viewer/ViewerAPIHandlers.swift:41 — Sources/SimUse/Viewer/ViewerAPIHandlers.swift:41-48 | Sources/SimUse/Viewer/ViewerAPIHandlers.swift:86-93 — 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) Sources/SimUseCore/SelectorFrameFilter.swift:140 — Sources/SimUseCore/SelectorFrameFilter.swift:140-147 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:258-265 — before extracting anything, compare `Sources/SimUseCore/SelectorFrameFilter.swift` and `Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 61 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 (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) Sources/AndroidBackend/Bridge/BridgeSession.swift:92 — Sources/AndroidBackend/Bridge/BridgeSession.swift:92-96 | Sources/SimUseCore/OutlineCache.swift:88-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) Sources/AndroidBackend/Normalizer/AndroidSelector.swift:170 — Sources/AndroidBackend/Normalizer/AndroidSelector.swift:170-174 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:122-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (5 lines × 2) Sources/SimUseCore/Daemon/DaemonCommand.swift:135 — Sources/SimUseCore/Daemon/DaemonCommand.swift:135-139 | Sources/SimUseCore/Daemon/DaemonCommand.swift:335-339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SimUseCore/Daemon/DaemonCommand.swift:135` 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/handler/PasteHandler.kt:65 — `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) Sources/iOSSimBackend/Sim/XcodeCompatibility.swift:66 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:909 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D3 · God Classes · FileTooLong · ×2
  • FileTooLong: A11y/AccessibilityFetcher.swift Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift — FileTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 197 over it, 1.39× 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: Normalizer/AndroidOutlineRenderer.swift Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift — FileTooLong — 522 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: AndroidOutlineRenderer (10-1083). The bar is 500 significant lines; this is 22 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.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×2
  • Edited copy of a member (22 corresponding lines) Sources/iOSSimBackend/Normalizer/ListDetector.swift:216 — Sources/iOSSimBackend/Normalizer/ListDetector.swift:216-237 | Sources/iOSSimBackend/Normalizer/ListDetector.swift:304-333 — 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.
  • Edited copy of a member (22 corresponding lines) Sources/iOSSimBackend/A11y/AccessibilityPoller.swift:37 — Sources/iOSSimBackend/A11y/AccessibilityPoller.swift:37-58 | Sources/iOSSimBackend/A11y/AccessibilityPoller.swift:60-83 — 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 copy of a member (19 corresponding lines) · ×2
  • Edited copy of a member (19 corresponding lines) Sources/SimUseVideo/MPEGTSMuxer.swift:272 — Sources/SimUseVideo/MPEGTSMuxer.swift:272-290 | Sources/SimUseVideo/MPEGTSMuxer.swift:293-313 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) Sources/iOSSimBackend/Sim/Setup.swift:10 — Sources/iOSSimBackend/Sim/Setup.swift:10-28 | Sources/iOSSimBackend/Sim/SimulatorUtilities.swift:7-25 — 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 (14 corresponding lines) · ×2
  • Edited copy of a member (14 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:840 — Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:840-853 | Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:382-396 — 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) Sources/iOSSimBackend/A11y/SoftKeyboardDetector.swift:105 — Sources/iOSSimBackend/A11y/SoftKeyboardDetector.swift:105-128 | Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift:427-440 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×2
  • Edited copy of a member (12 corresponding lines) Sources/SimUseCore/SwipeCoordinates.swift:124 — Sources/SimUseCore/SwipeCoordinates.swift:124-138 | Sources/SimUseCore/TapCoordinates.swift:46-57 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:80 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:80-91 | Sources/SimUse/Commands/RecordVideo.swift:105-116 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) Sources/iOSSimBackend/Sim/ResizableAppSession.swift:204 — Sources/iOSSimBackend/Sim/ResizableAppSession.swift:204-214 | Sources/iOSSimBackend/Sim/SimulatorDisplayTopology.swift:304-314 — 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) Sources/iOSSimBackend/Sim/ResizableAppSession.swift:132 — Sources/iOSSimBackend/Sim/ResizableAppSession.swift:132-142 | Sources/iOSSimBackend/Sim/SimulatorDisplayTopology.swift:197-207 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 3+ corresponding lines) Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift:114 — Sources/AndroidBackend/Verbs/AndroidMultiTouchCommand.swift:114-116 | Sources/SimUse/Commands/MultiTouch.swift:111-113 | Sources/iOSSimBackend/Verbs/IOSSimMultiTouchCommand.swift:165-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 3+ corresponding lines) Sources/SimUse/Commands/SpikeDaemon.swift:169 — Sources/SimUse/Commands/SpikeDaemon.swift:169-171 | Sources/SimUseCore/Daemon/DaemonServer.swift:335-337 | Sources/iOSSimBackend/Util/PerfLog.swift:101-103 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (14 lines × 5) · ×2
  • Duplicated block (14 lines × 5) Sources/SimUse/Commands/Button.swift:60 — Sources/SimUse/Commands/Button.swift:60-73 | Sources/SimUse/Commands/LongPress.swift:78-91 | Sources/SimUse/Commands/Paste.swift:102-115 | Sources/SimUse/Commands/Touch.swift:99-112 | Sources/SimUse/Commands/Type.swift:79-92 — 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 5 call sites, so a change lands once.
  • Duplicated block (14 lines × 5) Sources/SimUse/Commands/Gesture.swift:132 — Sources/SimUse/Commands/Gesture.swift:132-145 | Sources/SimUse/Commands/MultiTouch.swift:125-138 | Sources/SimUse/Commands/RecordVideo.swift:68-81 | Sources/SimUse/Commands/StreamVideo.swift:100-113 | Sources/SimUse/Commands/Swipe.swift:76-89 — 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 5 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×2
  • Duplicated block (12 lines × 2) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:371 — Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:371-382 | Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:232-243 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:371` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) Sources/SimUseCore/SelectorFrameFilter.swift:150 — Sources/SimUseCore/SelectorFrameFilter.swift:150-161 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:268-279 — before extracting anything, compare `Sources/SimUseCore/SelectorFrameFilter.swift` and `Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 61 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 (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:133 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:133-143 | Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:114-124 — before extracting anything, compare `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift` and `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:133` 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
  • Duplicated block (11 lines × 2) Sources/SimUse/Commands/LongPress.swift:108 — Sources/SimUse/Commands/LongPress.swift:108-118 | Sources/SimUse/Commands/Tap.swift:138-148 — 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.
D1 · Cyclomatic Complexity · GesturePreset.validateOptions (cyclomatic 43) · ×1
  • GesturePreset.validateOptions (cyclomatic 43) Sources/SimUseCore/GesturePreset.swift:318 — GesturePreset.validateOptions has cyclomatic complexity 43 (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 · PasteboardProcess.blockingRun (cyclomatic 37) · ×1
  • PasteboardProcess.blockingRun (cyclomatic 37) Sources/iOSSimBackend/Sim/PasteboardProcess.swift:45 — PasteboardProcess.blockingRun has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AndroidOutlineRenderer.includeNode (cyclomatic 36) · ×1
  • AndroidOutlineRenderer.includeNode (cyclomatic 36) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:469 — AndroidOutlineRenderer.includeNode has cyclomatic complexity 36 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · TapTargetingOptions.validate (cyclomatic 33) · ×1
  • TapTargetingOptions.validate (cyclomatic 33) Sources/SimUseCore/Options/TapTargetingOptions.swift:71 — TapTargetingOptions.validate 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 · PasteEditMenu.presentation (cyclomatic 30) · ×1
  • PasteEditMenu.presentation (cyclomatic 30) Sources/iOSSimBackend/A11y/PasteEditMenu.swift:249 — PasteEditMenu.presentation has cyclomatic complexity 30 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · IOSSimTapCommand.performTap (cyclomatic 30) · ×1
  • IOSSimTapCommand.performTap (cyclomatic 30) Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift:163 — IOSSimTapCommand.performTap has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CollapsedChildrenRecovery.runProbes (cyclomatic 29) · ×1
  • CollapsedChildrenRecovery.runProbes (cyclomatic 29) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:841 — CollapsedChildrenRecovery.runProbes 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.
D1 · Cyclomatic Complexity · AndroidOutlineRenderer.foldContainerText (cyclomatic 28) · ×1
  • AndroidOutlineRenderer.foldContainerText (cyclomatic 28) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:650 — AndroidOutlineRenderer.foldContainerText has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AndroidSelectorResolver.resolve (cyclomatic 27) · ×1
  • AndroidSelectorResolver.resolve (cyclomatic 27) Sources/AndroidBackend/Normalizer/AndroidSelector.swift:278 — AndroidSelectorResolver.resolve has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · ShellTokenizer.tokenize (cyclomatic 27) · ×1
  • ShellTokenizer.tokenize (cyclomatic 27) Sources/iOSSimBackend/Util/ShellTokenizer.swift:22 — ShellTokenizer.tokenize has cyclomatic complexity 27 (threshold 15). Of this number, 25 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AndroidStreamVideoCommand.streamH264 (cyclomatic 26) · ×1
  • AndroidStreamVideoCommand.streamH264 (cyclomatic 26) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:192 — AndroidStreamVideoCommand.streamH264 has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AndroidOutlineRenderer.render (cyclomatic 25) · ×1
  • AndroidOutlineRenderer.render (cyclomatic 25) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:57 — AndroidOutlineRenderer.render has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · IOSSimPasteCommand.validateOptions (cyclomatic 25) · ×1
  • IOSSimPasteCommand.validateOptions (cyclomatic 25) Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift:136 — IOSSimPasteCommand.validateOptions has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · OrientationCalibrator.calibrate (cyclomatic 24) · ×1
  • OrientationCalibrator.calibrate (cyclomatic 24) Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:161 — OrientationCalibrator.calibrate has cyclomatic complexity 24 (threshold 15). Of this number, 23 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AndroidRecordVideoCommand.recordVideoAndroidStream (cyclomatic 23) · ×1
  • AndroidRecordVideoCommand.recordVideoAndroidStream (cyclomatic 23) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:204 — AndroidRecordVideoCommand.recordVideoAndroidStream has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SelectorFrameFilter.init (cyclomatic 22) · ×1
  • SelectorFrameFilter.init (cyclomatic 22) Sources/SimUseCore/SelectorFrameFilter.swift:93 — SelectorFrameFilter.init 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 · CollapsedChildrenRecovery.computeBlindZones (cyclomatic 22) · ×1
  • CollapsedChildrenRecovery.computeBlindZones (cyclomatic 22) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:1050 — CollapsedChildrenRecovery.computeBlindZones 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 · FrameFilter.init (cyclomatic 22) · ×1
  • FrameFilter.init (cyclomatic 22) Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:211 — FrameFilter.init 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 · ActionRouter.dispatch (cyclomatic 21) · ×1
  • ActionRouter.dispatch (cyclomatic 21) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:87 — ActionRouter.dispatch has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · OutlineFormatter.render (cyclomatic 20) · ×1
  • OutlineFormatter.render (cyclomatic 20) Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:75 — OutlineFormatter.render 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 · OutlineSideBars.bar (cyclomatic 20) · ×1
  • OutlineSideBars.bar (cyclomatic 20) Sources/iOSSimBackend/Normalizer/OutlineSideBars.swift:82 — OutlineSideBars.bar has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 belong to 2 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 · SimulatorDisplayTopologyProbe.display (cyclomatic 19) · ×1
  • SimulatorDisplayTopologyProbe.display (cyclomatic 19) Sources/iOSSimBackend/Sim/SimulatorDisplayTopology.swift:211 — SimulatorDisplayTopologyProbe.display has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · OutlineAliasResolver.resolveWithPayload (cyclomatic 18) · ×1
  • OutlineAliasResolver.resolveWithPayload (cyclomatic 18) Sources/SimUseCore/OutlineAliasResolver.swift:173 — OutlineAliasResolver.resolveWithPayload 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 · OrientationCalibrator.resolveSceneOffset (cyclomatic 18) · ×1
  • OrientationCalibrator.resolveSceneOffset (cyclomatic 18) Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:341 — OrientationCalibrator.resolveSceneOffset has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AndroidOutlineRenderer.computeIndentLayout (cyclomatic 17) · ×1
  • AndroidOutlineRenderer.computeIndentLayout (cyclomatic 17) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:946 — AndroidOutlineRenderer.computeIndentLayout 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 · AndroidStreamVideoCommand.streamJPEGFrames (cyclomatic 17) · ×1
  • AndroidStreamVideoCommand.streamJPEGFrames (cyclomatic 17) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:334 — AndroidStreamVideoCommand.streamJPEGFrames 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 · HttpServer.parseRequest (cyclomatic 17) · ×1
  • HttpServer.parseRequest (cyclomatic 17) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/HttpServer.kt:153 — HttpServer.parseRequest 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 · BridgeConnection.resolveBridgeHost (cyclomatic 16) · ×1
  • BridgeConnection.resolveBridgeHost (cyclomatic 16) Sources/AndroidBackend/Bridge/BridgeConnection.swift:76 — BridgeConnection.resolveBridgeHost has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · GesturePreset.validateOptions (cognitive 62) · ×1
  • GesturePreset.validateOptions (cognitive 62) Sources/SimUseCore/GesturePreset.swift:318 — GesturePreset.validateOptions has cognitive complexity 62 (threshold 15). Drivers by points: if/else 33 (51 pts), boolean chains 9, match/switch 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CollapsedChildrenRecovery.runProbes (cognitive 58) · ×1
  • CollapsedChildrenRecovery.runProbes (cognitive 58) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:841 — CollapsedChildrenRecovery.runProbes has cognitive complexity 58 (threshold 15). Drivers by points: if/else 16 (34 pts), loops 6 (13 pts), ternaries 2 (5 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 29). 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 · TapTargetingOptions.validate (cognitive 55) · ×1
  • TapTargetingOptions.validate (cognitive 55) Sources/SimUseCore/Options/TapTargetingOptions.swift:71 — TapTargetingOptions.validate has cognitive complexity 55 (threshold 15). Drivers by points: if/else 21 (38 pts), boolean chains 7, error handling 2 (5 pts), match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PasteboardProcess.blockingRun (cognitive 54) · ×1
  • PasteboardProcess.blockingRun (cognitive 54) Sources/iOSSimBackend/Sim/PasteboardProcess.swift:45 — PasteboardProcess.blockingRun has cognitive complexity 54 (threshold 15). Drivers by points: if/else 19 (36 pts), boolean chains 12, loops 4 (5 pts), error handling 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ShellTokenizer.tokenize (cognitive 51) · ×1
  • ShellTokenizer.tokenize (cognitive 51) Sources/iOSSimBackend/Util/ShellTokenizer.swift:22 — ShellTokenizer.tokenize has cognitive complexity 51 (threshold 15). Drivers by points: if/else 17 (43 pts), boolean chains 4, match/switch 2 (3 pts), loops 1 (nesting depth added 27). Of this number, 49 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AndroidOutlineRenderer.foldContainerText (cognitive 50) · ×1
  • AndroidOutlineRenderer.foldContainerText (cognitive 50) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:650 — AndroidOutlineRenderer.foldContainerText has cognitive complexity 50 (threshold 15). Drivers by points: if/else 15 (33 pts), boolean chains 8, loops 5 (7 pts), ternaries 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IOSSimTapCommand.performTap (cognitive 48) · ×1
  • IOSSimTapCommand.performTap (cognitive 48) Sources/iOSSimBackend/Verbs/IOSSimTapCommand.swift:163 — IOSSimTapCommand.performTap has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (30 pts), error handling 3 (8 pts), boolean chains 4, ternaries 3 (4 pts), match/switch 1 (2 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 · AndroidOutlineRenderer.render (cognitive 47) · ×1
  • AndroidOutlineRenderer.render (cognitive 47) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:57 — AndroidOutlineRenderer.render has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 5 (8 pts), boolean chains 6, ternaries 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 · AndroidStreamVideoCommand.streamH264 (cognitive 42) · ×1
  • AndroidStreamVideoCommand.streamH264 (cognitive 42) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:192 — AndroidStreamVideoCommand.streamH264 has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (28 pts), boolean chains 8, loops 2 (3 pts), error handling 1 (2 pts), ternaries 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 · AndroidOutlineRenderer.includeNode (cognitive 39) · ×1
  • AndroidOutlineRenderer.includeNode (cognitive 39) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:469 — AndroidOutlineRenderer.includeNode has cognitive complexity 39 (threshold 15). Drivers by points: boolean chains 24, if/else 11 (15 pts) (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · AndroidRecordVideoCommand.recordVideoAndroidStream (cognitive 35) · ×1
  • AndroidRecordVideoCommand.recordVideoAndroidStream (cognitive 35) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:204 — AndroidRecordVideoCommand.recordVideoAndroidStream has cognitive complexity 35 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 6, error handling 2 (3 pts), loops 2 (3 pts), ternaries 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 · SelectorFrameFilter.init (cognitive 35) · ×1
  • SelectorFrameFilter.init (cognitive 35) Sources/SimUseCore/SelectorFrameFilter.swift:93 — SelectorFrameFilter.init has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 9, loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FrameFilter.init (cognitive 35) · ×1
  • FrameFilter.init (cognitive 35) Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:211 — FrameFilter.init has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 9, loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AndroidSelectorResolver.resolve (cognitive 34) · ×1
  • AndroidSelectorResolver.resolve (cognitive 34) Sources/AndroidBackend/Normalizer/AndroidSelector.swift:278 — AndroidSelectorResolver.resolve has cognitive complexity 34 (threshold 15). Drivers by points: if/else 22 (27 pts), boolean chains 7 (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 · CollapsedChildrenRecovery.computeBlindZones (cognitive 33) · ×1
  • CollapsedChildrenRecovery.computeBlindZones (cognitive 33) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:1050 — CollapsedChildrenRecovery.computeBlindZones has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 6 (9 pts), boolean chains 6, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PasteEditMenu.presentation (cognitive 33) · ×1
  • PasteEditMenu.presentation (cognitive 33) Sources/iOSSimBackend/A11y/PasteEditMenu.swift:249 — PasteEditMenu.presentation has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 21, if/else 7 (11 pts), loops 1 (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · AndroidOutlineRenderer.computeIndentLayout (cognitive 31) · ×1
  • AndroidOutlineRenderer.computeIndentLayout (cognitive 31) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:946 — AndroidOutlineRenderer.computeIndentLayout has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 5 (6 pts), boolean chains 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 · HttpServer.parseRequest (cognitive 29) · ×1
  • HttpServer.parseRequest (cognitive 29) bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/HttpServer.kt:153 — HttpServer.parseRequest has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16 (23 pts), error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OrientationCalibrator.calibrate (cognitive 28) · ×1
  • OrientationCalibrator.calibrate (cognitive 28) Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:161 — OrientationCalibrator.calibrate has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 11, loops 1 (nesting depth added 5). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OutlineFormatter.render (cognitive 27) · ×1
  • OutlineFormatter.render (cognitive 27) Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:75 — OutlineFormatter.render has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 4 (7 pts), boolean chains 5, ternaries 1 (nesting depth added 6). 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 · IOSSimPasteCommand.validateOptions (cognitive 27) · ×1
  • IOSSimPasteCommand.validateOptions (cognitive 27) Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift:136 — IOSSimPasteCommand.validateOptions has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 13 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · BridgeClient.verifiedEndpoint (cognitive 25) · ×1
  • BridgeClient.verifiedEndpoint (cognitive 25) Sources/AndroidBackend/Bridge/BridgeClient.swift:125 — BridgeClient.verifiedEndpoint has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (3 pts), error handling 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, loops 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 · OrientationCalibrator.resolveSceneOffset (cognitive 25) · ×1
  • OrientationCalibrator.resolveSceneOffset (cognitive 25) Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:341 — OrientationCalibrator.resolveSceneOffset has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 8, loops 2 (3 pts), ternaries 1 (nesting depth added 8). Of this number, 24 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AndroidStreamVideoCommand.streamJPEGFrames (cognitive 23) · ×1
  • AndroidStreamVideoCommand.streamJPEGFrames (cognitive 23) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:334 — AndroidStreamVideoCommand.streamJPEGFrames has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, match/switch 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IOSSimTapCommand.toBatchPrimitives (cognitive 22) · ×1
  • IOSSimTapCommand.toBatchPrimitives (cognitive 22) Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift:37 — IOSSimTapCommand.toBatchPrimitives has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuthTokenFetcher.fetchEndpoint (cognitive 21) · ×1
  • AuthTokenFetcher.fetchEndpoint (cognitive 21) Sources/AndroidBackend/Adb/AuthTokenFetcher.swift:75 — AuthTokenFetcher.fetchEndpoint has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OutlineAliasResolver.resolveWithPayload (cognitive 21) · ×1
  • OutlineAliasResolver.resolveWithPayload (cognitive 21) Sources/SimUseCore/OutlineAliasResolver.swift:173 — OutlineAliasResolver.resolveWithPayload has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 3, match/switch 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IOSSimStreamVideoCommand.streamCompressedFrames (cognitive 21) · ×1
  • IOSSimStreamVideoCommand.streamCompressedFrames (cognitive 21) Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:197 — IOSSimStreamVideoCommand.streamCompressedFrames has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 1 (3 pts), error handling 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AndroidProcessLister.parse (cognitive 20) · ×1
  • AndroidProcessLister.parse (cognitive 20) Sources/AndroidBackend/Adb/AndroidProcessLister.swift:35 — AndroidProcessLister.parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 3, 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 · AuthTokenFetcher.parseEndpoint (cognitive 20) · ×1
  • AuthTokenFetcher.parseEndpoint (cognitive 20) Sources/AndroidBackend/Adb/AuthTokenFetcher.swift:45 — AuthTokenFetcher.parseEndpoint has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 3, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AndroidRecordVideoCommand.recordVideoAndroidScreencapLegacy (cognitive 20) · ×1
  • AndroidRecordVideoCommand.recordVideoAndroidScreencapLegacy (cognitive 20) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:391 — AndroidRecordVideoCommand.recordVideoAndroidScreencapLegacy has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · OutlineAliasResolver.parse (cognitive 20) · ×1
  • OutlineAliasResolver.parse (cognitive 20) Sources/SimUseCore/OutlineAliasResolver.swift:114 — OutlineAliasResolver.parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SimulatorDisplayTopologyProbe.display (cognitive 20) · ×1
  • SimulatorDisplayTopologyProbe.display (cognitive 20) Sources/iOSSimBackend/Sim/SimulatorDisplayTopology.swift:211 — SimulatorDisplayTopologyProbe.display has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 7, match/switch 1 (2 pts), ternaries 1 (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · AndroidSelectorError.errorDescription (cognitive 19) · ×1
  • AndroidSelectorError.errorDescription (cognitive 19) Sources/AndroidBackend/Normalizer/AndroidSelector.swift:80 — AndroidSelectorError.errorDescription has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 1, 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 · SimUseExecutableCommand.run (cognitive 19) · ×1
  • SimUseExecutableCommand.run (cognitive 19) Sources/SimUseCore/Types/SimUseExecutableCommand.swift:93 — SimUseExecutableCommand.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 2 (4 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 · StdoutStreamSink.write (cognitive 19) · ×1
  • StdoutStreamSink.write (cognitive 19) Sources/SimUseVideo/StdoutStreamSink.swift:56 — StdoutStreamSink.write has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HIDInteractor.getOrCreateHIDConnection (cognitive 19) · ×1
  • HIDInteractor.getOrCreateHIDConnection (cognitive 19) Sources/iOSSimBackend/HID/HIDInteractor.swift:265 — HIDInteractor.getOrCreateHIDConnection has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · IOSSimStreamVideoCommand.streamNative (cognitive 19) · ×1
  • IOSSimStreamVideoCommand.streamNative (cognitive 19) Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:290 — IOSSimStreamVideoCommand.streamNative has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 2 (3 pts), loops 1 (2 pts), boolean chains 1, match/switch 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 · BridgeConnection.resolveBridgeHost (cognitive 18) · ×1
  • BridgeConnection.resolveBridgeHost (cognitive 18) Sources/AndroidBackend/Bridge/BridgeConnection.swift:76 — BridgeConnection.resolveBridgeHost has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 7, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · AndroidOutlineRenderer.dropRedundantOuter (cognitive 18) · ×1
  • AndroidOutlineRenderer.dropRedundantOuter (cognitive 18) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:775 — AndroidOutlineRenderer.dropRedundantOuter has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, loops 3 (4 pts), ternaries 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 · SoftKeyboardDetector.classify (cognitive 18) · ×1
  • SoftKeyboardDetector.classify (cognitive 18) Sources/iOSSimBackend/A11y/SoftKeyboardDetector.swift:134 — SoftKeyboardDetector.classify has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 6, 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 · ResizableAppSessionMonitor.state (cognitive 18) · ×1
  • ResizableAppSessionMonitor.state (cognitive 18) Sources/iOSSimBackend/Sim/ResizableAppSession.swift:229 — ResizableAppSessionMonitor.state has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 7 (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 · IOSSimRecordVideoCommand.recordVideoViaScreenshots (cognitive 18) · ×1
  • IOSSimRecordVideoCommand.recordVideoViaScreenshots (cognitive 18) Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:235 — IOSSimRecordVideoCommand.recordVideoViaScreenshots has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 2 (4 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 · DaemonServer.acceptReady (cognitive 17) · ×1
  • DaemonServer.acceptReady (cognitive 17) Sources/SimUseCore/Daemon/DaemonServer.swift:110 — DaemonServer.acceptReady has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 3, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GesturePresetsView.body (cognitive 17) · ×1
  • GesturePresetsView.body (cognitive 17) Playgrounds/iOS/SimUsePlayground/Views/GesturePresetsView.swift:111 — GesturePresetsView.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, ternaries 4 (7 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · OutlineSideBars.bar (cognitive 17) · ×1
  • OutlineSideBars.bar (cognitive 17) Sources/iOSSimBackend/Normalizer/OutlineSideBars.swift:82 — OutlineSideBars.bar has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 5, match/switch 2. Of this number, 11 points are the body's own statements and 6 belong to 2 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.
D2 · Cognitive Complexity · SpikeDaemon.run (cognitive 16) · ×1
  • SpikeDaemon.run (cognitive 16) Sources/SimUse/Commands/SpikeDaemon.swift:47 — SpikeDaemon.run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CollapsedChildrenRecovery.walk (cognitive 16) · ×1
  • CollapsedChildrenRecovery.walk (cognitive 16) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:718 — CollapsedChildrenRecovery.walk has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, loops 3 (6 pts), if/else 3 (4 pts) (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 · IOSSimBatchCommand.execute (cognitive 16) · ×1
  • IOSSimBatchCommand.execute (cognitive 16) Sources/iOSSimBackend/Verbs/IOSSimBatchCommand.swift:191 — IOSSimBatchCommand.execute has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 2 (4 pts), boolean chains 1, loops 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 · IOSSimSwipeCommand.validateTimingOptions (cognitive 16) · ×1
  • IOSSimSwipeCommand.validateTimingOptions (cognitive 16) Sources/iOSSimBackend/Verbs/IOSSimSwipeCommand.swift:88 — IOSSimSwipeCommand.validateTimingOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: AndroidOutlineRenderer Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:10 — ClassTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 120 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.
D3 · God Classes · TooManyMethods · ×1
  • TooManyMethods: BridgeClient Sources/AndroidBackend/Bridge/BridgeClient.swift:29 — TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (3 members, 24 shared lines) · ×1
  • Near-duplicate member family (3 members, 24 shared lines) Sources/AndroidBackend/Adb/Adb.swift:178 — Sources/AndroidBackend/Adb/Adb.swift:178-280 | Sources/iOSSimBackend/Sim/DevicectlQuery.swift:59-106 | Sources/iOSSimBackend/Sim/SimctlDeviceLister.swift:35-84 — These 3 members are variants of one another: a block of 24 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication · Near-duplicate member pair (35 shared lines) · ×1
  • Near-duplicate member pair (35 shared lines) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:391 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:391-472 | Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:235-292 — These two members are variants of one another: 35 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 · Edited copy of a member (78 corresponding lines) · ×1
  • Edited copy of a member (78 corresponding lines) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:334 — Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:334-418 | Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:197-274 — These two members are one piece of code written twice and then edited apart: 78 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) Sources/SimUseCore/SelectorFrameFilter.swift:93 — Sources/SimUseCore/SelectorFrameFilter.swift:93-136 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:211-254 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift:81 — Sources/AndroidBackend/Verbs/AndroidLongPressCommand.swift:81-114 | Sources/SimUse/Commands/Tap.swift:159-186 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:408 — Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:408-439 | Sources/iOSSimBackend/A11y/OrientationCalibrator.swift:566-596 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:823 — Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:823-838 | Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:348-378 — 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 (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) Sources/iOSSimBackend/A11y/DisplayOrientation.swift:128 — Sources/iOSSimBackend/A11y/DisplayOrientation.swift:128-148 | Sources/iOSSimBackend/A11y/DisplayOrientation.swift:155-175 — 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 copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) Sources/iOSSimBackend/Sim/BundleIdentifierResolver.swift:56 — Sources/iOSSimBackend/Sim/BundleIdentifierResolver.swift:56-67 | Sources/iOSSimBackend/Sim/BundleIdentifierResolver.swift:76-90 | Sources/iOSSimBackend/Sim/BundleIdentifierResolver.swift:124-134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 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) · ×1
  • Edited copy of a member (17 corresponding lines) Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift:97 — Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift:97-113 | Sources/SimUse/Commands/Swipe.swift:119-137 — 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 · Edited copies of one member (3 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 28+ corresponding lines) Sources/iOSSimBackend/Verbs/IOSSimMultiTouchCommand.swift:135 — Sources/iOSSimBackend/Verbs/IOSSimMultiTouchCommand.swift:135-163 | Sources/iOSSimBackend/Verbs/IOSSimSwipeCommand.swift:88-123 | Sources/iOSSimBackend/Verbs/IOSSimTouchCommand.swift:94-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 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, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) Sources/SimUse/Commands/Devices.swift:129 — Sources/SimUse/Commands/Devices.swift:129-143 | Sources/SimUse/Commands/Devices.swift:145-157 | Sources/SimUse/Commands/Devices.swift:159-173 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 12+ corresponding lines) Sources/AndroidBackend/Normalizer/AndroidSelector.swift:474 — Sources/AndroidBackend/Normalizer/AndroidSelector.swift:474-486 | Sources/AndroidBackend/Normalizer/AndroidSelector.swift:488-503 | Sources/AndroidBackend/Normalizer/AndroidSelector.swift:505-516 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:502-517 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:534-545 — These 5 members are one piece of code written 5 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 5 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) Sources/SimUseCore/Daemon/DaemonProtocol.swift:46 — Sources/SimUseCore/Daemon/DaemonProtocol.swift:46-52 | Sources/SimUseCore/Daemon/DaemonProtocol.swift:82-89 | Sources/SimUseCore/Daemon/DaemonProtocol.swift:114-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) Sources/AndroidBackend/Bridge/BridgeClient.swift:240 — Sources/AndroidBackend/Bridge/BridgeClient.swift:240-243 | Sources/AndroidBackend/Bridge/BridgeClient.swift:263-267 | Sources/AndroidBackend/Bridge/BridgeClient.swift:293-297 — 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, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) Sources/AndroidBackend/Verbs/AndroidGestureCommand.swift:62 — Sources/AndroidBackend/Verbs/AndroidGestureCommand.swift:62-82 | Sources/SimUse/Commands/Gesture.swift:112-130 | Sources/iOSSimBackend/Verbs/IOSSimGestureCommand.swift:110-128 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 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 (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) Sources/SimUse/Commands/Paste.swift:91 — Sources/SimUse/Commands/Paste.swift:91-100 | Sources/iOSSimBackend/Verbs/IOSSimPasteCommand.swift:123-132 — 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 copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:87 — Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift:87-94 | Sources/SimUse/Commands/StreamVideo.swift:67-75 | Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:130-137 — 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 · Duplicated block (24–27 lines × 3) · ×1
  • Duplicated block (24–27 lines × 3) Sources/AndroidBackend/Adb/Adb.swift:182 — Sources/AndroidBackend/Adb/Adb.swift:182-208 | Sources/iOSSimBackend/Sim/DevicectlQuery.swift:65-88 | Sources/iOSSimBackend/Sim/SimctlDeviceLister.swift:37-60 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Sources/AndroidBackend/Adb/Adb.swift:216` calls `DispatchSemaphore`, `signal` and `Sources/iOSSimBackend/Sim/DevicectlQuery.swift:90` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:754 — Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:754-775 | Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:794-815 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:754` 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–17 lines × 2) · ×1
  • Duplicated block (15–17 lines × 2) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:456 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:456-472 | Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:278-292 — before extracting anything, compare `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift` and `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:456` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15–16 lines × 3) · ×1
  • Duplicated block (15–16 lines × 3) Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:84 — Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:84-98 | Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift:68-83 | Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift:146-160 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:83` calls `setup` and `Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift:67` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:1024 — Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:1024-1038 | Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:503-517 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:1024` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) Sources/SimUseCore/SelectorFrameFilter.swift:93 — Sources/SimUseCore/SelectorFrameFilter.swift:93-120 | Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift:211-238 — before extracting anything, compare `Sources/SimUseCore/SelectorFrameFilter.swift` and `Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/SimUseCore/SelectorFrameFilter.swift:93` 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–12 lines × 5) · ×1
  • Duplicated block (7–12 lines × 5) Sources/iOSSimBackend/Verbs/IOSSimFoldCommand.swift:83 — Sources/iOSSimBackend/Verbs/IOSSimFoldCommand.swift:83-89 | Sources/iOSSimBackend/Verbs/IOSSimKeyComboCommand.swift:58-66 | Sources/iOSSimBackend/Verbs/IOSSimKeyCommand.swift:54-65 | Sources/iOSSimBackend/Verbs/IOSSimKeySequenceCommand.swift:45-53 | Sources/iOSSimBackend/Verbs/IOSSimRotateCommand.swift:59-65 — 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 5 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift:104 — Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift:104-113 | Sources/SimUse/Commands/Swipe.swift:126-137 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift:104` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/AndroidBackend/Verbs/AndroidSwipeCommand.swift:102` calls `max`, `Int`, `rounded` and `Sources/SimUse/Commands/Swipe.swift:124` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–11 lines × 2) · ×1
  • Duplicated block (8–11 lines × 2) Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:1048 — Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift:1048-1055 | Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:531-541 — 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 (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) Sources/AndroidBackend/Normalizer/TruncationHelpers.swift:22 — Sources/AndroidBackend/Normalizer/TruncationHelpers.swift:22-29 | Sources/iOSSimBackend/Normalizer/OutlineFormatter.swift:571-580 — 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) Sources/iOSSimBackend/Sim/ResizableAppSession.swift:118 — Sources/iOSSimBackend/Sim/ResizableAppSession.swift:118-126 | Sources/iOSSimBackend/Sim/SimulatorDisplayTopology.swift:188-195 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Sources/iOSSimBackend/Sim/ResizableAppSession.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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:440 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:440-447 | Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:270-276 — before extracting anything, compare `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift` and `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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 (7 lines × 2) · ×1
  • Duplicated block (7 lines × 2) Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:152 — Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:152-158 | Sources/iOSSimBackend/A11y/AccessibilityFetcher.swift:399-405 — 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 (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:73 — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:73-78 | Sources/iOSDeviceBackend/Verbs/IOSDeviceCommand.swift:370-375 | Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:70-75 | Sources/iOSSimBackend/Verbs/IOSSimScreenshotCommand.swift:59-64 — before extracting anything, compare `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift` and `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:69` calls `validate` and `Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift:68` 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: SimUseCore — SimUseCore: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: KeyCaptureUIView (LCOM4 5) Playgrounds/iOS/SimUsePlayground/Views/KeyPressView.swift:140 — KeyCaptureUIView's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P12 · CI test-gate honesty · Coverage collected but not gated · ×1
  • Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.
R2 · Cyclomatic Complexity · Complex function onKey (cyclomatic 20, cognitive 29) · ×1
  • Complex function onKey (cyclomatic 20, cognitive 29) Tools/Viewer/src/App.tsx:158 — onKey has cyclomatic complexity 20 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function App (cyclomatic 17, cognitive 15) · ×1
  • Complex function App (cyclomatic 17, cognitive 15) Tools/Viewer/src/App.tsx:6 — App has cyclomatic complexity 17 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 (anonymous) (cyclomatic 14, cognitive 21) · ×1
  • Complex function (anonymous) (cyclomatic 14, cognitive 21) Tools/Viewer/src/App.tsx:136 — (anonymous) has cyclomatic complexity 14 and cognitive complexity 21; 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 ElementBox (cyclomatic 13, cognitive 11) · ×1
  • Complex function ElementBox (cyclomatic 13, cognitive 11) Tools/Viewer/src/Canvas.tsx:240 — ElementBox 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 Details (cyclomatic 11, cognitive 10) · ×1
  • Complex function Details (cyclomatic 11, cognitive 10) Tools/Viewer/src/Details.tsx:23 — Details 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.
R3 · Large Files · Tools/Viewer/src/Canvas.tsx · ×1
  • Tools/Viewer/src/Canvas.tsx: 452 lines of code Tools/Viewer/src/Canvas.tsx:1 — Tools/Viewer/src/Canvas.tsx has 452 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · No lint script · ×1
  • No lint script — test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Minor — 22 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×6
  • Duplicated predicate Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:427 — `Task.isCancelled || cancellationFlag.isCancelled()` appears character-identically in 4 files — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift, Sources/AndroidBackend/Verbs/AndroidStreamVideoCommand.swift, Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift, Sources/iOSSimBackend/Verbs/IOSSimStreamVideoCommand.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:240 — `Task.isCancelled || cancellationFlag.isCancelled() || fatalBox.first != nil` appears character-identically in 2 files — Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift, Sources/iOSSimBackend/Verbs/IOSSimRecordVideoCommand.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift:271 — `index < parsedKeycodes.count - 1 && keyDelay > 0` appears character-identically in 2 files — Sources/iOSSimBackend/Batch/Command+BatchConvertible.swift, Sources/iOSSimBackend/Verbs/IOSSimKeySequenceCommand.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Sources/SimUseCore/SelectorFrameFilter.swift:46 — `minX == nil && maxX == nil && minY == nil && maxY == nil && minXRel == nil && maxXRel == nil && minYRel == nil && maxYRel == nil` appears character-identically in 2 files — Sources/SimUseCore/SelectorFrameFilter.swift, Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Sources/SimUseCore/SelectorFrameFilter.swift:51 — `minXRel != nil || maxXRel != nil || minYRel != nil || maxYRel != nil` appears character-identically in 2 files — Sources/SimUseCore/SelectorFrameFilter.swift, Sources/iOSSimBackend/A11y/AccessibilityTargetResolver.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate Sources/AndroidBackend/Normalizer/AndroidListDetector.swift:160 — `outer.x <= inner.x && outer.y <= inner.y && outer.x + outer.width >= inner.x + inner.width && outer.y + outer.height >= inner.y + inner.heig…` appears character-identically in 2 files — Sources/AndroidBackend/Normalizer/AndroidListDetector.swift, Sources/AndroidBackend/Normalizer/AndroidOutlineRenderer.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X7 · Silent fallback defaults · Silent fallback default in catch · ×4
  • Silent fallback default in catch bridge/app/src/main/java/com/linecorp/simuse/devicebridge/server/ActionRouter.kt:593 — `parseStrokes` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
  • Silent fallback default in catch Sources/AndroidBackend/Verbs/AndroidRecordVideoCommand.swift:312 — `detectSDK` turns every thrown error into `30` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
  • Silent fallback default in catch Sources/SimUseCore/DaemonPaths.swift:207 — `enumerateLiveDaemons` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
  • Silent fallback default in catch Sources/iOSSimBackend/Sim/BundleIdentifierResolver.swift:23 — `resolve` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
D34 · Knowledge Freshness · Orphaned file · ×3
  • Orphaned file Sources/SimUseVideo/AnnexBStreamParser.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 Sources/iOSDeviceBackend/AXAudit/AXAuditValue.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 Sources/iOSDeviceBackend/AXAudit/AXAuditAttribute.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.
D21 · Naming Consistency · `resolveOnPATH` spells `PATH` where 35 names in the project spell it `Path` · ×1
  • `resolveOnPATH` spells `PATH` where 35 names in the project spell it `Path` Sources/AndroidBackend/Adb/Adb.swift:286 — 35 of 36 names in project AndroidBackend spell the token `Path` (35 of 36; unit: names in project AndroidBackend containing `Path`). Peers: ContentView.navigationPath (Playgrounds/iOS/SimUsePlayground/ContentView.swift:13); SwipeTestView.currentPath (Playgrounds/iOS/SimUsePlayground/Views/SwipeTestView.swift:14); repository.SwipePath (Playgrounds/iOS/SimUsePlayground/Views/SwipeTestView.swift:195); repository.SwipePathView (Playgrounds/iOS/SimUsePlayground/Views/SwipeTestView.swift:205); repository.SwipePathShape (Playgrounds/iOS/SimUsePlayground/Views/SwipeTestView.swift:311). Rename to `resolveOnPath`. [rule N6]
D21 · Naming Consistency · `iosHidButton` spells `Hid` where 14 names in the project spell it `HID` · ×1
  • `iosHidButton` spells `Hid` where 14 names in the project spell it `HID` Sources/iOSSimBackend/Verbs/IOSSimButtonCommand.swift:33 — 14 of 15 names in project AndroidBackend spell the token `HID` (14 of 15; unit: names in project AndroidBackend containing `HID`). Peers: iOSSimBackend.ResolvedHIDTarget (Sources/iOSSimBackend/A11y/AccessibilityPoller.swift:21); AccessibilityPoller.resolveWithPollingHIDTarget (Sources/iOSSimBackend/A11y/AccessibilityPoller.swift:85); iOSSimBackend.FBSimulatorHIDEvent (Sources/iOSSimBackend/HID/FBSimulatorHIDEvent+Sendable.swift:8); HIDInteractor.performHIDEvent (Sources/iOSSimBackend/HID/HIDInteractor.swift:136); HIDInteractor.performHIDEventOnce (Sources/iOSSimBackend/HID/HIDInteractor.swift:167). Rename to `iosHIDButton`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 6.0/10. The most over is `(repository root)` (35300 LoC, 504 module-visible types across 29 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.
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 3 of 196 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 196 of the 244 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: Sources/SimUseVideo/AnnexBStreamParser.swift, Sources/iOSDeviceBackend/AXAudit/AXAuditValue.swift, Sources/iOSDeviceBackend/AXAudit/AXAuditAttribute.swift. 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
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:21 — 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 1 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 Tools/Viewer/package.json:12 — `Tools/Viewer/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`.
Minor — 3 finding(s)
D10 · Test Quality · Skipped (documented) · ×2
  • Skipped (documented): swipeFromLeftEdge Tests/GestureTests.swift:75 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
  • Skipped (documented): swipeFromRightEdge Tests/GestureTests.swift:93 — Skipped with a documented reason — a deferral, not lazy debt: wrapped in withKnownIssue — the body is expected to fail, so its failure is not reported
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: swift-argument-parser — `swift-argument-parser` is resolved at 1.5.0, but 1.8.2 is the newest release tagged on https://github.com/apple/swift-argument-parser within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update swift-argument-parser` reaches this one with no change to Package.swift.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-7ebdf4d317c24ddf9ada82a7e8cca8be/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-7ebdf4d317c24ddf9ada82a7e8cca8be/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 .11artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .1artifacts/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: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `Playgrounds/iOS/SimUsePlayground/ContentView.swift`, `Playgrounds/iOS/SimUsePlayground/Views/TouchControlView.swift`, `Sources/SimUse/Viewer/ViewerAPIHandlers.swift`, `Sources/SimUseCore/ReleaseVersion.swift`, `Sources/iOSDeviceBackend/Domain/DeviceTreeFetcher.swift`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1dd0a-ab78-732b-bae6-c3b9b29f0444 · 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