Public report of hatayama/unity-cli-loop, published 17 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, 17 November 2026, 08:34 UTC · Survey ID cd_d161c6adb1f54e388484e78c95dc998c

hatayama/unity-cli-loop

Measured 17 November 2026, 08:33 UTC, at code version 1bf7354

First survey, so nothing to compare with yet Boundary Type-Coupling: not measured

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 67.7out of 100 Adequate
CriticalWeakAdequateStrongExemplary

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

A large codebase: 217,762 lines of product code in 54 projects, tests not counted · Estimated rebuild effort: about 5.2 person-years · Weakest lens: Performance, 60.0

Findings by how serious they are

17 critical 272 serious 73 minor

4 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
17 November 2026, 08:33 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.
327of 362 findings point to an exact file and line, so you can open each one in the code. The other 35 concern the repository as a whole, such as missing documentation.
55dimensions across 6 lenses, read from 217,762 lines of product code in 54 projects.
Chapters

Executive summary

hatayama/unity-cli-loop falls short of our standard for production, held back most by its Performance lens, the way the code guards its speed and its use of resources. It scores 67.7 out of 100 and is rated Adequate, and eight of its 17 critical findings are security problems in the build pipeline and in its automatic dependency updates.

Performance, at 60.0, is the weakest lens and counts most in the score. The best first step is removing the blocking calls, worth about 7.2 points. Removing the test references comes next, worth about 4.5 points. Raising Performance to 70 would lift the score to about 71.3.

Four pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Two pipeline steps run downloads nobody checks, and five sets of files in separate parts keep changing together, which points to hidden dependencies. Passing outside input through environment variables, checking each download against a checksum and making the hidden dependencies explicit would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The four pieces of product code that depend on test code need their reference to the test project removed.

The product code is 217,762 lines, about €760,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.
Performance 60.0 · counts for 46%Architecture 65.5 · counts for 25%Security and Compliance 74.9 · counts for 14%Production Readiness 87.4 · counts for 8%Maturity 88.5 · counts for 4%Code Health 96.7 · counts for 2%

If Performance rose from 60.0 to 70, the lowest score rated Strong, the score would rise from 67.7 to about 71.3.

Code composition: what the lines of code are
Business logic 13%Supporting code 16%Tests 71%
Rebuild cost: about €760,000 · Estimate
Cost to rebuild€250,000 to €1,300,000, for 4,203 to 13,411 hours of work, about 5.2 person-years for 3 to 10 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 68. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 217,762 lines of product code
Comment linesThe estimate prices 198,860 lines. Comment lines count towards the size of 217,762 lines but aren't priced as work.
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.

Top priorities

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

1
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Raises the score by about 7.2 points · Medium effort · Async & latency hygiene
2
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
Raises the score by about 4.5 points · Medium effort · Test isolation
3
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with CompileCheckWorker.UnitTests.csproj.
Raises the score by about 0.8 points · Low effort · Platform End-of-Life

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 €760,000 to build again, about 5.2 person-years of work. Its weakest lens is Performance, at 60.0 (Adequate). Performance is about whether the code is written and measured with speed in mind. Because the weakest lens counts most in the score, work on Performance also moves the score most.
Based on: the rebuild estimate · the Performance grade · how much each lens counts
What to do: Start with the Performance actions in Top priorities.
If you do one thing first · First action
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(). Of all the actions in this report, it raises the score most for the work it takes: about 7.2 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

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

arch UnityCLILoop.Application Application UnityCLILoop.Domain Domain UnityCLILoop.Application->UnityCLILoop.Domain UnityCLILoop.ToolContracts ToolContracts UnityCLILoop.Application->UnityCLILoop.ToolContracts UnityCLILoop.Dev Dev UnityCLILoop.Dev->UnityCLILoop.Application UnityCLILoop.Dev->UnityCLILoop.Domain UnityCLILoop.FirstPartyTools.Common.InputRecording.Editor Editor UnityCLILoop.Dev->UnityCLILoop.FirstPartyTools.Common.InputRecording.Editor UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor Editor UnityCLILoop.Dev->UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor UnityCLILoop.FirstPartyTools.Common.Overlay.Editor Editor UnityCLILoop.Dev->UnityCLILoop.FirstPartyTools.Common.Overlay.Editor UnityCLILoop.FirstPartyTools.Compile.Editor Editor UnityCLILoop.Dev->UnityCLILoop.FirstPartyTools.Compile.Editor UnityCLILoop.FirstPartyTools.Editor Editor UnityCLILoop.Dev->UnityCLILoop.FirstPartyTools.Editor UnityCLILoop.FirstPartyTools.ExecuteDynamicCode.Editor Editor UnityCLILoop.Dev->UnityCLILoop.FirstPartyTools.ExecuteDynamicCode.Editor UnityCLILoop.FirstPartyTools.Screenshot.Editor Editor UnityCLILoop.Dev->UnityCLILoop.FirstPartyTools.Screenshot.Editor UnityCLILoop.Runtime Runtime UnityCLILoop.Dev->UnityCLILoop.Runtime UnityCLILoop.Dev->UnityCLILoop.ToolContracts UnityCLILoop.Domain->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.Common.InputRecording.Editor->UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor UnityCLILoop.FirstPartyTools.Common.InputRecording.Editor->UnityCLILoop.FirstPartyTools.Common.Overlay.Editor UnityCLILoop.FirstPartyTools.Common.InputRecording.Editor->UnityCLILoop.Runtime UnityCLILoop.FirstPartyTools.Common.InputRecording.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor->UnityCLILoop.Application UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor->UnityCLILoop.Runtime UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.Common.Overlay.Editor->UnityCLILoop.Runtime UnityCLILoop.FirstPartyTools.Common.Preflight.Editor Editor UnityCLILoop.PausePoints.Runtime Runtime UnityCLILoop.FirstPartyTools.Common.Preflight.Editor->UnityCLILoop.PausePoints.Runtime UnityCLILoop.FirstPartyTools.Common.Preflight.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.Compile.Editor->UnityCLILoop.Domain UnityCLILoop.FirstPartyTools.Compile.Editor->UnityCLILoop.PausePoints.Runtime UnityCLILoop.FirstPartyTools.Compile.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.Compile.Editor UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.ExecuteDynamicCode.Editor UnityCLILoop.FirstPartyTools.HotReload.Editor Editor UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.HotReload.Editor UnityCLILoop.FirstPartyTools.RecordInput.Editor Editor UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.RecordInput.Editor UnityCLILoop.FirstPartyTools.ReplayInput.Editor Editor UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.ReplayInput.Editor UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.Screenshot.Editor UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor Editor UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor Editor UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor Editor UnityCLILoop.FirstPartyTools.Editor->UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor UnityCLILoop.FirstPartyTools.ExecuteDynamicCode.Editor->UnityCLILoop.Application UnityCLILoop.FirstPartyTools.ExecuteDynamicCode.Editor->UnityCLILoop.Domain UnityCLILoop.FirstPartyTools.ExecuteDynamicCode.Editor->UnityCLILoop.PausePoints.Runtime UnityCLILoop.FirstPartyTools.ExecuteDynamicCode.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.HotReload.Editor->UnityCLILoop.FirstPartyTools.ExecuteDynamicCode.Editor UnityCLILoop.FirstPartyTools.HotReload.Editor->UnityCLILoop.PausePoints.Runtime UnityCLILoop.FirstPartyTools.HotReload.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.RecordInput.Editor->UnityCLILoop.Application UnityCLILoop.FirstPartyTools.RecordInput.Editor->UnityCLILoop.FirstPartyTools.Common.InputRecording.Editor UnityCLILoop.FirstPartyTools.RecordInput.Editor->UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor UnityCLILoop.FirstPartyTools.RecordInput.Editor->UnityCLILoop.FirstPartyTools.Common.Overlay.Editor UnityCLILoop.FirstPartyTools.RecordInput.Editor->UnityCLILoop.FirstPartyTools.Common.Preflight.Editor UnityCLILoop.FirstPartyTools.RecordInput.Editor->UnityCLILoop.Runtime UnityCLILoop.FirstPartyTools.RecordInput.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.ReplayInput.Editor->UnityCLILoop.FirstPartyTools.Common.InputRecording.Editor UnityCLILoop.FirstPartyTools.ReplayInput.Editor->UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor UnityCLILoop.FirstPartyTools.ReplayInput.Editor->UnityCLILoop.FirstPartyTools.Common.Overlay.Editor UnityCLILoop.FirstPartyTools.ReplayInput.Editor->UnityCLILoop.FirstPartyTools.Common.Preflight.Editor UnityCLILoop.FirstPartyTools.ReplayInput.Editor->UnityCLILoop.Runtime UnityCLILoop.FirstPartyTools.ReplayInput.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.Screenshot.Editor->UnityCLILoop.Application UnityCLILoop.FirstPartyTools.Screenshot.Editor->UnityCLILoop.FirstPartyTools.Common.Overlay.Editor UnityCLILoop.FirstPartyTools.Screenshot.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor->UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor->UnityCLILoop.FirstPartyTools.Common.Overlay.Editor UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor->UnityCLILoop.FirstPartyTools.Common.Preflight.Editor UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor->UnityCLILoop.PausePoints.Runtime UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor->UnityCLILoop.Runtime UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor->UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor->UnityCLILoop.FirstPartyTools.Common.Overlay.Editor UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor->UnityCLILoop.FirstPartyTools.Common.Preflight.Editor UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor->UnityCLILoop.PausePoints.Runtime UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor->UnityCLILoop.Runtime UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor->UnityCLILoop.ToolContracts UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor->UnityCLILoop.Application UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor->UnityCLILoop.FirstPartyTools.Common.InputSystem.Editor UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor->UnityCLILoop.FirstPartyTools.Common.Overlay.Editor UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor->UnityCLILoop.FirstPartyTools.Common.Preflight.Editor UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor->UnityCLILoop.PausePoints.Runtime UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor->UnityCLILoop.Runtime UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor->UnityCLILoop.ToolContracts __more__ +34 more projects

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.

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

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 Assets.Util2 UnityCliLoop.CodeComplexity3 UnityCliLoop.DeadCodeScanner4 github.com/hatayama/unity-cli-loop/common/clicontract5 github.com/hatayama/unity-cli-loop/common/clitest6 github.com/hatayama/unity-cli-loop/common/ipcendpoint7 github.com/hatayama/unity-cli-loop/common/product8 github.com/hatayama/unity-cli-loop/common/progress9 github.com/hatayama/unity-cli-loop/common/skillscan10 github.com/hatayama/unity-cli-loop/common/tools11 github.com/hatayama/unity-cli-loop/common/unityprocess12 github.com/hatayama/unity-cli-loop/common/unityprocess/unitydialog13 github.com/hatayama/unity-cli-loop/common/version14 github.com/hatayama/unity-cli-loop/common/vibelog15 github.com/hatayama/unity-cli-loop/dispatcher/attestation16 github.com/hatayama/unity-cli-loop/dispatcher/cmd/dispatcher17 github.com/hatayama/unity-cli-loop/dispatcher/cmd/refresh-attestation-trusted-root18 github.com/hatayama/unity-cli-loop/dispatcher/dispatchercontract19 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck/fastcheck20 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck/resultstore21 github.com/hatayama/unity-cli-loop/dispatcher/internal/filelock22 github.com/hatayama/unity-cli-loop/dispatcher/internal/install23 github.com/hatayama/unity-cli-loop/dispatcher/internal/nativepath24 github.com/hatayama/unity-cli-loop/dispatcher/internal/projectverify25 github.com/hatayama/unity-cli-loop/dispatcher/internal/uninstall26 github.com/hatayama/unity-cli-loop/dispatcher/internal/update27 github.com/hatayama/unity-cli-loop/project-runner/cmd/project-runner28 github.com/hatayama/unity-cli-loop/tools/release-automation/cmd/cancel-superseded-waiting-runs29 github.com/hatayama/unity-cli-loop/common/skilldocs30 github.com/hatayama/unity-cli-loop/common/tooldocs31 github.com/hatayama/unity-cli-loop/common/ui32 github.com/hatayama/unity-cli-loop/common/unityipc33 github.com/hatayama/unity-cli-loop/common/errors34 github.com/hatayama/unity-cli-loop/common/project35 github.com/hatayama/unity-cli-loop/tools/release-automation/internal/automation36 github.com/hatayama/unity-cli-loop/common/clicore37 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck38 github.com/hatayama/unity-cli-loop/dispatcher/internal/githubapi39 github.com/hatayama/unity-cli-loop/dispatcher/internal/dispatcher40 github.com/hatayama/unity-cli-loop/project-runner/internal/projectrunner
1 Assets.Util
2 UnityCliLoop.CodeComplexity
3 UnityCliLoop.DeadCodeScanner
4 github.com/hatayama/unity-cli-loop/common/clicontract
5 github.com/hatayama/unity-cli-loop/common/clitest
6 github.com/hatayama/unity-cli-loop/common/ipcendpoint
7 github.com/hatayama/unity-cli-loop/common/product
8 github.com/hatayama/unity-cli-loop/common/progress
9 github.com/hatayama/unity-cli-loop/common/skillscan
10 github.com/hatayama/unity-cli-loop/common/tools
11 github.com/hatayama/unity-cli-loop/common/unityprocess
12 github.com/hatayama/unity-cli-loop/common/unityprocess/unitydialog
13 github.com/hatayama/unity-cli-loop/common/version
14 github.com/hatayama/unity-cli-loop/common/vibelog
15 github.com/hatayama/unity-cli-loop/dispatcher/attestation
16 github.com/hatayama/unity-cli-loop/dispatcher/cmd/dispatcher
17 github.com/hatayama/unity-cli-loop/dispatcher/cmd/refresh-attestation-trusted-root
18 github.com/hatayama/unity-cli-loop/dispatcher/dispatchercontract
19 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck/fastcheck
20 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck/resultstore
21 github.com/hatayama/unity-cli-loop/dispatcher/internal/filelock
22 github.com/hatayama/unity-cli-loop/dispatcher/internal/install
23 github.com/hatayama/unity-cli-loop/dispatcher/internal/nativepath
24 github.com/hatayama/unity-cli-loop/dispatcher/internal/projectverify
25 github.com/hatayama/unity-cli-loop/dispatcher/internal/uninstall
26 github.com/hatayama/unity-cli-loop/dispatcher/internal/update
27 github.com/hatayama/unity-cli-loop/project-runner/cmd/project-runner
28 github.com/hatayama/unity-cli-loop/tools/release-automation/cmd/cancel-superseded-waiting-runs
29 github.com/hatayama/unity-cli-loop/common/skilldocs2
30 github.com/hatayama/unity-cli-loop/common/tooldocs2
31 github.com/hatayama/unity-cli-loop/common/ui1
32 github.com/hatayama/unity-cli-loop/common/unityipc1
33 github.com/hatayama/unity-cli-loop/common/errors14
34 github.com/hatayama/unity-cli-loop/common/project2
35 github.com/hatayama/unity-cli-loop/tools/release-automation/internal/automation21
36 github.com/hatayama/unity-cli-loop/common/clicore21213
37 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck2594
38 github.com/hatayama/unity-cli-loop/dispatcher/internal/githubapi2
39 github.com/hatayama/unity-cli-loop/dispatcher/internal/dispatcher12154111837
40 github.com/hatayama/unity-cli-loop/project-runner/internal/projectrunner14212121963
Uses a module listed above itPart of a loopThe module itself
1 Assets.Util2 UnityCliLoop.CodeComplexity3 UnityCliLoop.DeadCodeScanner4 github.com/hatayama/unity-cli-loop/common/clicontract5 github.com/hatayama/unity-cli-loop/common/clitest6 github.com/hatayama/unity-cli-loop/common/ipcendpoint7 github.com/hatayama/unity-cli-loop/common/product8 github.com/hatayama/unity-cli-loop/common/progress9 github.com/hatayama/unity-cli-loop/common/skillscan10 github.com/hatayama/unity-cli-loop/common/tools11 github.com/hatayama/unity-cli-loop/common/unityprocess12 github.com/hatayama/unity-cli-loop/common/unityprocess/unitydialog13 github.com/hatayama/unity-cli-loop/common/version14 github.com/hatayama/unity-cli-loop/common/vibelog15 github.com/hatayama/unity-cli-loop/dispatcher/attestation16 github.com/hatayama/unity-cli-loop/dispatcher/cmd/dispatcher17 github.com/hatayama/unity-cli-loop/dispatcher/cmd/refresh-attestation-trusted-root18 github.com/hatayama/unity-cli-loop/dispatcher/dispatchercontract19 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck/fastcheck20 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck/resultstore21 github.com/hatayama/unity-cli-loop/dispatcher/internal/filelock22 github.com/hatayama/unity-cli-loop/dispatcher/internal/install23 github.com/hatayama/unity-cli-loop/dispatcher/internal/nativepath24 github.com/hatayama/unity-cli-loop/dispatcher/internal/projectverify25 github.com/hatayama/unity-cli-loop/dispatcher/internal/uninstall26 github.com/hatayama/unity-cli-loop/dispatcher/internal/update27 github.com/hatayama/unity-cli-loop/project-runner/cmd/project-runner28 github.com/hatayama/unity-cli-loop/tools/release-automation/cmd/cancel-superseded-waiting-runs29 github.com/hatayama/unity-cli-loop/common/skilldocs30 github.com/hatayama/unity-cli-loop/common/tooldocs31 github.com/hatayama/unity-cli-loop/common/ui32 github.com/hatayama/unity-cli-loop/common/unityipc33 github.com/hatayama/unity-cli-loop/common/errors34 github.com/hatayama/unity-cli-loop/common/project35 github.com/hatayama/unity-cli-loop/tools/release-automation/internal/automation36 github.com/hatayama/unity-cli-loop/common/clicore37 github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck38 github.com/hatayama/unity-cli-loop/dispatcher/internal/githubapi39 github.com/hatayama/unity-cli-loop/dispatcher/internal/dispatcher40 github.com/hatayama/unity-cli-loop/project-runner/internal/projectrunnerAssets.Util1UnityCliLoop.CodeComplexity2UnityCliLoop.DeadCodeScanner3github.com/hatayama/unity-cli-loop/common/clicontract4github.com/hatayama/unity-cli-loop/common/clitest5github.com/hatayama/unity-cli-loop/common/ipcendpoint6github.com/hatayama/unity-cli-loop/common/product7github.com/hatayama/unity-cli-loop/common/progress8github.com/hatayama/unity-cli-loop/common/skillscan9github.com/hatayama/unity-cli-loop/common/tools10github.com/hatayama/unity-cli-loop/common/unityprocess11github.com/hatayama/unity-cli-loop/common/unityprocess/unitydialog12github.com/hatayama/unity-cli-loop/common/version13github.com/hatayama/unity-cli-loop/common/vibelog14github.com/hatayama/unity-cli-loop/dispatcher/attestation15github.com/hatayama/unity-cli-loop/dispatcher/cmd/dispatcher16github.com/hatayama/unity-cli-loop/dispatcher/cmd/refresh-attestation-trusted-root17github.com/hatayama/unity-cli-loop/dispatcher/dispatchercontract18github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck/fastcheck19github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck/resultstore20github.com/hatayama/unity-cli-loop/dispatcher/internal/filelock21github.com/hatayama/unity-cli-loop/dispatcher/internal/install22github.com/hatayama/unity-cli-loop/dispatcher/internal/nativepath23github.com/hatayama/unity-cli-loop/dispatcher/internal/projectverify24github.com/hatayama/unity-cli-loop/dispatcher/internal/uninstall25github.com/hatayama/unity-cli-loop/dispatcher/internal/update26github.com/hatayama/unity-cli-loop/project-runner/cmd/project-runner27github.com/hatayama/unity-cli-loop/tools/release-automation/cmd/cancel-superseded-waiting-runs28github.com/hatayama/unity-cli-loop/common/skilldocs29github.com/hatayama/unity-cli-loop/common/tooldocs30github.com/hatayama/unity-cli-loop/common/ui31github.com/hatayama/unity-cli-loop/common/unityipc32github.com/hatayama/unity-cli-loop/common/errors33github.com/hatayama/unity-cli-loop/common/project34github.com/hatayama/unity-cli-loop/tools/release-automation/internal/automation35github.com/hatayama/unity-cli-loop/common/clicore36github.com/hatayama/unity-cli-loop/dispatcher/internal/compilecheck37github.com/hatayama/unity-cli-loop/dispatcher/internal/githubapi38github.com/hatayama/unity-cli-loop/dispatcher/internal/dispatcher39github.com/hatayama/unity-cli-loop/project-runner/internal/projectrunner4022111422121213259421215411183714212121963+31 more modules (most-connected shown)

At a glance — Code Health · 96.7 · Exemplary ·

At a glance — Architecture · 65.5 · Adequate · gated by AX8 ·

At a glance — Maturity · 88.5 · Strong ·

At a glance — Readiness · 87.4 · Strong ·

At a glance — Security · 74.9 · Adequate · gated by D29 ·

At a glance — Performance · 60.0 · Adequate ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection18High / Critical
A03:2025 — Software Supply Chain Failures11Medium

Roadmap

Top priorities: Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult(); Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse; Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.

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

Do thisHelpsEffortDimension
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().+7.2 ptsMediumAsync & latency hygiene
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.+4.5 ptsMediumTest isolation
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with CompileCheckWorker.UnitTests.csproj.+0.8 ptsLowPlatform End-of-Life
Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with PausePointStatusBridgeCommand.cs (3), UloopPausePointEntry.cs, PausePointTools.cs.+0.7 ptsLowChange Coupling
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.+1.2 ptsMediumCryptographic Hygiene
Resolve the 1 `skillscan.FindUnityCliLoopPackage` signals absence with comma-ok `(T,… finding(s) in Internal API Consistency — start with packages.go.+0.4 ptsLowInternal API Consistency
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+0.4 ptsLowStatic Analysis (SAST)
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).+0.4 ptsLowStatic Analysis (SAST)

File quality

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

FileScoreBandWorst signal
REDACTED2.7SlopStatic Analysis (SAST): High: REDACTED
cli/project-runner/internal/projectrunner/pause_point_enable.go5.6MixedCognitive Complexity: projectrunner.extractPausePointEnableAwaitFlags (cognitive 17)
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
cli/common/skillscan/packages.go6.3MixedCode Duplication: Edited copy of a member (18 corresponding lines)
REDACTED6.3MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED6.3MixedDependency Vulnerabilities: Medium CVE: REDACTED
Packages/src/Editor/Infrastructure/Api/PausePointStatusBridgeCommand.cs6.5MixedChange Coupling: Boundary-crossing change coupling: PausePointStatusBridgeCommand.cs ↔ UloopPausePointEntry.cs
Packages/src/Editor/Presentation/Setup/SetupWizardWindow.cs7.0MixedGod Classes: TooManyMethods: SetupWizardWindow
cli/project-runner/internal/projectrunner/compile_attach.go7.1MixedCognitive Complexity: projectrunner.waitForAttachedCompileCompletion (cognitive 20)
cli/dispatcher/internal/dispatcher/compile_check.go7.1MixedCode Duplication: Edited copy of a member (18 corresponding lines)
Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/Execution/AwaitableHelper.cs7.2MixedCyclomatic Complexity: AwaitableHelper.ConvertValueTaskToTask (cyclomatic 16)
cli/dispatcher/internal/dispatcher/skills.go7.2MixedCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
cli/release-automation/internal/automation/contract_file_at_ref.go7.2MixedCode Duplication: Edited copies of one member (3 members, 16+ corresponding lines)
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs7.4MixedCyclomatic Complexity: CommandLineOptions.TryParse (cyclomatic 19)
cli/project-runner/internal/projectrunner/control_play_mode_wait.go7.4MixedCognitive Complexity: projectrunner.waitForControlPlayModeState (cognitive 26)
Packages/src/Editor/Domain/ThirdPartyToolMigrationDeclarationNameRules.cs7.4MixedCognitive Complexity: ThirdPartyToolMigrationDeclarationNameRules.IsTupleTypeClose (cognitive 20)
cli/dispatcher/attestation/verifier.go7.4MixedCode Duplication: Edited copy of a member (36 corresponding lines)
cli/release-automation/internal/automation/dispatcher_pin_freshness.go7.4MixedCode Duplication: Edited copy of a member (32 corresponding 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 — 17

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

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

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

Could not be resolved — 4

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
D1D2D3D4D5D6D7D10D11D12D13D14D17D19D20D22D24D26D27D28D29D30D34D35D36D37D43D44AX10AX3AX4AX5AX6AX8GD1IC1M1M2M3M4P1P10P3P4P6PF3S1X1X12X16X2X27X29X3X5

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, 327 of 362 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 01a1e8a3-8f29-7a92-9f69-96ce988a2559.

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.

  • D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 38 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cs (166,990 lines, 75% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .cs, .go, and our analyzer cannot run the .go test suite(s) — so no coverage was collected for the repository as a whole. The .NET half did build and run, and its own line coverage came back at 97.8% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
  • D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 8,528 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 390 test source file(s) (.go) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • 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 Unity UPM manifest (Packages/manifest.json or a package's package.json), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Upm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (554951 line(s) across the 90-day window), but no complexity could be computed for .cs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
  • 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 (8 contributor(s) across 2457 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 7 hold 0.1% 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.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .cs (166,990 lines, 75% of production source), .go (53,966 lines, 24% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • D23 Boundary Type-Coupling — 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. Large codebase (221,549 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — 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.
  • IC1 Incompleteness & stubs — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • 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.
  • X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X2 Cancellation propagation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X27 Collection changed while being enumerated — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.

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.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • 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.
  • 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.
  • D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages 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 (REDACTED, 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.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity9.5 / 10Stronggated by 3 serious findings✓ 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 9.5 / 10 · rule-coverage 100% · ceiling Prevented

3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CommandLineOptions.TryParse at 19. A further 1 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 ReferencePublicizer.ExposeInternalsOfType at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Packages/src/Editor/FirstPartyTools/HotReload/Patching/ReferencePublicizer.cs (ReferencePublicizer.ExposeInternalsOfType 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.

CommandLineOptions.TryParse (cyclomatic 19)tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs:31
AwaitableHelper.ConvertValueTaskToTask (cyclomatic 16)Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/Execution/AwaitableHelper.cs:327
AwaitableHelper.ConvertGenericValueTaskToTask (cyclomatic 16)Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/Execution/AwaitableHelper.cs:428

What to do

  1. Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with CommandLineOptions.TryParse (cyclomatic 19), AwaitableHelper.ConvertValueTaskToTask (cyclomatic 16), AwaitableHelper.ConvertGenericValueTaskToTask (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 9.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

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

72 method(s) exceeded the cognitive complexity threshold of 15; the worst was CommandLineOptions.TryParse at 42.

CommandLineOptions.TryParse (cognitive 42)tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs:31
projectrunner.buildToolParams (cognitive 30)cli/project-runner/internal/projectrunner/tool_params.go:15
dispatcher.resolveDispatcherLatestReleaseTag (cognitive 29)cli/dispatcher/internal/dispatcher/attestation_release.go:57
AutoUsingResolver.ResolveAsync (cognitive 26)Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/AutoUsingResolver.cs:22
projectrunner.waitForControlPlayModeState (cognitive 26)cli/project-runner/internal/projectrunner/control_play_mode_wait.go:166

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

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with CommandLineOptions.TryParse (cognitive 42). — Refactoring it lifts Cognitive Complexity from 6.9 to about 7.3/10.

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

D3 · God Classes9.6 / 10Stronggated by 17 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.6 / 10 · rule-coverage 100% · ceiling Prevented

17 god class(es) detected.

MethodTooLong: CompiledAssemblyBuilder.BuildAsync · ×9Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/CompiledAssemblyBuilder.cs:74
TooManyMethods: HotReloadFileGeneration · ×5Packages/src/Editor/FirstPartyTools/HotReload/Patching/HotReloadFileGeneration.cs
TooManyFields: pausePointStatusResponsecli/project-runner/internal/projectrunner/pause_point_types.go:3
ClassTooLong: HotReloadConstantsPackages/src/Editor/FirstPartyTools/HotReload/Shared/HotReloadConstants.cs
FunctionTooLong: projectrunner.sendWithTransientConnectionRetryAttemptscli/project-runner/internal/projectrunner/connection_retry.go:255

What to do

  1. Resolve the 9 MethodTooLong finding(s) in God Classes — start with CompiledAssemblyBuilder.cs, HotReloadPatchTargetSupport.cs, HotReloadOrchestrator.cs. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 5 TooManyMethods finding(s) in God Classes — start with HotReloadFileGeneration.cs, ThirdPartyToolMigrationWizardWindow.cs, SetupWizardWindow.cs. — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 1 TooManyFields finding(s) in God Classes — start with pause_point_types.go. — 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 Duplication9.3 / 10Stronggated by 127 serious findings✓ Tool-verified

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

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

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

38 duplicated block group(s) detected. 1.7 % of the production lines (3,732 of 221,549) are in a reported copy. A further 89 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 8 of the 127 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .cs (75% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.

Edited copy of a member (14 corresponding lines) · ×7cli/common/unityprocess/unitydialog/inspect.go:113
Edited copy of a member (8 corresponding lines) · ×7cli/dispatcher/internal/install/command.go:81
Edited copy of a member (16 corresponding lines) · ×5cli/common/skillscan/sources.go:65
Edited copy of a member (11 corresponding lines) · ×5cli/release-automation/cmd/stamp-dispatcher-pin/main.go:43
Edited copy of a member (9 corresponding lines) · ×5cli/dispatcher/internal/dispatcher/launch_ready.go:196

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

What to do

  1. Resolve the 7 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with inspect.go, main.go, dispatcher_freshness.go. — One of this dimension's main actionable groups (7 warning-level).
  2. Resolve the 7 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with command.go, publish_coverage_trend.go, coverage_report.go. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 5 Edited copy of a member (16 corresponding lines) finding(s) in Code Duplication — start with sources.go, bootstrap.go, pause_point_trigger.go. — 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 · Coupling7.5 / 10Strong✓ Tool-verified

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

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

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

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

54 production modules (Go+Unity), 0 dependency cycle(s), 11 unstable depended-on module(s). Read from the build's own module declarations; 14 module(s) off the main sequence, with abstractness counted on 50 of the 54 (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: Unity.InternalAPIEditorBridge.024 · ×3
Unstable project UnityCLILoop.FirstPartyTools.Editor
Unstable project UnityCLILoop.FirstPartyTools.HotReload.Editor
Unstable project UnityCLILoop.FirstPartyTools.HotReload.Patching.Editor
Unstable project UnityCLILoop.FirstPartyTools.RecordInput.Editor

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

What to do

  1. Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 1 Unstable project UnityCLILoop.FirstPartyTools.Editor finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project UnityCLILoop.FirstPartyTools.HotReload.Editor 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.9 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

2 of 393 classes have LCOM4 above 3.

Low cohesion: user32API (LCOM4 7) · ×2cli/common/unityprocess/focus_windows_user32.go:15

What to do

  1. Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with focus_windows_user32.go, ExecuteDynamicCodeResponse.cs. — One of this dimension's main actionable groups (2 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. Cycles found: 0.

Detailed fixes: d7_recommendation.md.

D10 · Test Quality10.0 / 10Stronggated by 1 serious finding✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 0 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8528 tests. Measured on the C# suite only — at least 390 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.

Fixed-sleep synchronisation: ReadLineAsync_WhenCanceledDuringWait_ShouldThrowAndAllowPipeClosetests/SharedRoslynCompilerWorker.UnitTests/SharedRoslynCompilerWorkerLineReaderTests.cs:67

What to do

  1. Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with SharedRoslynCompilerWorkerLineReaderTests.cs. — One of this dimension's main actionable groups (1 warning-level).

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

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 2 measured tier(s). .NET suite (the runs D8 measures coverage on): measured (0 flaky); Go (4 modules): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

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

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

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

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

1 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.

Outdated: golang.org/x/term

✓ 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 133 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 7 direct `PackageReference`(s), and 107 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Unity UPM manifest (Packages/manifest.json or a package's package.json), 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.

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

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

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

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

0 deducted debt markers + 0 dead symbols across 2388 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .cs, .go (100% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

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

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

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

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

2 of 2 documentation facets pass in full. 29 document(s) read across 72 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality9.7 / 10Exemplary✓ Tool-verified

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

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

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

2 of 24 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.

ADR has no Context sectiondocs/adr/0001-csharp-security-scan-engine.md:1detected by adr-integrity
ADR has no Consequences sectiondocs/adr/0002-dispatcher-runner-split.md:1detected by adr-integrity

✓ On the Gold path — maintain.

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

D22 · Internal API Consistency8.9 / 10Strong✓ Tool-verified

What it measures: Whether the internal API surface is consistent and coherent.

Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.

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

1 API inconsistencies among 91 exposed members measured against a convention their peers follow.

`skillscan.FindUnityCliLoopPackage` signals absence with comma-ok `(T, bool)` where its 3 sibling single-key reads use a bare `T` (the zero value when absent)cli/common/skillscan/packages.go:100

What to do

  1. Resolve the 1 `skillscan.FindUnityCliLoopPackage` signals absence with comma-ok `(T,… finding(s) in Internal API Consistency — start with packages.go. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d22_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 168 judged comments only repeat the code they sit on (0.0 %).

✓ On the Gold path — maintain.

Detailed fixes: d24_recommendation.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 of 9 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability9.9 / 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 9.9 / 10 · rule-coverage 100% · ceiling Documented

9 % of calls cross a namespace and 1 % go through an interface, but 92 % 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)2.0 / 10Critical✓ Tool-verified

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

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

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

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

18 finding(s): 0 critical, 8 high, 2 medium, 8 low. semgrep hit a parse error in 9 file(s) — `Assets/Tests/Editor/HotReload/HotReloadInitAccessorFixture.cs`, `scripts/check-go-cli-source.sh` (line 22), `scripts/soak-loop.sh` (line 339), `scripts/test-install-detect-asset-name.sh` (lines 96–115), `scripts/test-mark-release-pr-tagged.sh` (lines 15–158), … (+4 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D30 · Dependency Vulnerabilities9.4 / 10Stronggated by 8 serious findings✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling9.9 / 10Adequategated by 5 critical findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: SetupWizardWindow.cs↔CliSetupSection.cs 82%; pause_point_enable.go↔pause_point_types.go 70%; CliSetupSection.cs↔UnityCliLoopSettingsWindow.cs 64%

Boundary-crossing change coupling: PausePointStatusBridgeCommand.cs ↔ UloopPausePointEntry.cs · ×5Packages/src/Editor/Infrastructure/Api/PausePointStatusBridgeCommand.cs:1
Change coupling: SetupWizardWindow.cs ↔ CliSetupSection.cs · ×4Packages/src/Editor/Presentation/Setup/SetupWizardWindow.cs:1

What to do

  1. Resolve the 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with PausePointStatusBridgeCommand.cs (3), UloopPausePointEntry.cs, PausePointTools.cs. — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 4 Change coupling finding(s) in Change Coupling — start with SetupWizardWindow.cs, pause_point_enable.go, CliSetupSection.cs. — One of this dimension's main actionable groups (4 warning-level).

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

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

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

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

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

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — 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.

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.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-Life6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

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

End-of-life runtime: .NET net6.0tests/CompileCheckWorker.UnitTests/CompileCheckWorker.UnitTests.csproj:4

What to do

  1. Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with CompileCheckWorker.UnitTests.csproj. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

AX8 · Test isolation0.0 / 10Critical✓ 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.

  • `UnityCLILoop.Dev` (production) references the test project `UnityCLILoop.FirstPartyTools.RunTests.Editor`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `UnityCLILoop.Dev` (production) references the test project `UnityCLILoop.FirstPartyTools.RunTests.TestFramework.Editor`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `UnityCLILoop.FirstPartyTools.Editor` (production) references the test project `UnityCLILoop.FirstPartyTools.RunTests.Editor`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `UnityCLILoop.FirstPartyTools.Editor` (production) references the test project `UnityCLILoop.FirstPartyTools.RunTests.TestFramework.Editor`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.

What to do

  • Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

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

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

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

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

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

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

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

M2 · Architecture 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.

P3 · Security & performance tooling8.0 / 10Strong✓ Tool-verified

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

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

  • `REDACTED` schedules updates, but no `package-ecosystem` entry covers `nuget`, `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:3

What to do

  • Dependabot is configured but does not watch `nuget`, `npm` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

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

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

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

  • 5 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). (×5) — Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/SharedRoslynCompilerWorkerAssemblyBuilder.cs:130, Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/SharedRoslynCompilerWorkerAssemblyBuilder.cs:131, Packages/src/Editor/FirstPartyTools/HotReload/Shared/HotReloadSourceSnapshotCapture.cs:194, …

What to do

  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
S1 · Cryptographic Hygiene8.0 / 10Strong✓ Tool-verified

Other · Security — Cryptographic hygiene (weak hash/cipher, password key-derivation). This codebase has no web surface, so transport/header/cookie/CSRF controls are N/A and only crypto is scored.

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

  • MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses. — Packages/src/Editor/FirstPartyTools/HotReload/Shared/HotReloadSourceBaseline.cs:369

What to do

  • Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (`System.IO.Hashing.XxHash64`/`Crc32`) where it only derives an identifier such as a cache key or a mutex name.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X2 · Cancellation propagation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

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

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

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.

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

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

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

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

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

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.

X5 · Nullable reference types10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

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 Health96.7ExemplaryStrongest area.
Architecture65.5Adequate — gated by AX8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity88.5StrongSolid.
Readiness87.4StrongSolid.
Security74.9Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60.0AdequateLargest drag on the score — prioritise here.
Unscored — 5 check(s) recorded observations but carry no score

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

  • P12 CI test-gate honesty — 2 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.
  • SC1 Supply-chain hygiene — 11 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 31 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D15 Churn × Complexity Hotspots — complexity unreadable for .cs — churn × complexity hotspots could not be measured
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — Dimension evaluation failed
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — None of 1 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) — 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.
  • 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 — polyglot repository, one half has no runner
  • DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • 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
  • P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage data present for 16 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
  • 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.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X6 Hand-rolled structured-format parsing — 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 — 17 finding(s)
D35 · Change Coupling · Boundary-crossing change coupling · ×5
  • Boundary-crossing change coupling: PausePointStatusBridgeCommand.cs ↔ UloopPausePointEntry.cs Packages/src/Editor/Infrastructure/Api/PausePointStatusBridgeCommand.cs:1 — `Packages/src/Editor/Infrastructure/Api/PausePointStatusBridgeCommand.cs` (context Editor) and `Packages/src/Runtime/PausePoints/UloopPausePointEntry.cs` (context Runtime) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f5f4e339` feat: gate pause-point hits with the hit-when condition (#2405); `d1e3c21f` feat: report method entry counts for expired pause points (#2402); `779c32b5` feat: add a max-caller-frames option to enable-pause-point — run `git show` on any of them.
  • Boundary-crossing change coupling: PausePointStatusBridgeCommand.cs ↔ pause_point_types.go Packages/src/Editor/Infrastructure/Api/PausePointStatusBridgeCommand.cs:1 — `Packages/src/Editor/Infrastructure/Api/PausePointStatusBridgeCommand.cs` (context Editor) and `cli/project-runner/internal/projectrunner/pause_point_types.go` (context cli) sit in DIFFERENT parts of the tree yet change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `c8e1fe63` fix(pause-point): carry every warning in Warnings and point Message a…; `aee4288a` feat: list all markers when pause-point-status omits --id (#2413); `f5f4e339` feat: gate pause-point hits with the hit-when condition (#2405) — run `git show` on any of them.
  • Boundary-crossing change coupling: PausePointStatusBridgeCommand.cs ↔ pause_point_wait.go Packages/src/Editor/Infrastructure/Api/PausePointStatusBridgeCommand.cs:1 — `Packages/src/Editor/Infrastructure/Api/PausePointStatusBridgeCommand.cs` (context Editor) and `cli/project-runner/internal/projectrunner/pause_point_wait.go` (context cli) sit in DIFFERENT parts of the tree yet change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c8e1fe63` fix(pause-point): carry every warning in Warnings and point Message a…; `aee4288a` feat: list all markers when pause-point-status omits --id (#2413); `c0d7a93d` fix: Pause points no longer expire before await-pause-point can obser… — run `git show` on any of them.
  • Boundary-crossing change coupling: UloopPausePointEntry.cs ↔ pause_point_types.go Packages/src/Runtime/PausePoints/UloopPausePointEntry.cs:1 — `Packages/src/Runtime/PausePoints/UloopPausePointEntry.cs` (context Runtime) and `cli/project-runner/internal/projectrunner/pause_point_types.go` (context cli) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `f5f4e339` feat: gate pause-point hits with the hit-when condition (#2405); `d1e3c21f` feat: report method entry counts for expired pause points (#2402); `779c32b5` feat: add a max-caller-frames option to enable-pause-point — run `git show` on any of them.
  • Boundary-crossing change coupling: PausePointTools.cs ↔ UloopPausePointEntry.cs Packages/src/Editor/FirstPartyTools/PausePoint/PausePointTools.cs:1 — `Packages/src/Editor/FirstPartyTools/PausePoint/PausePointTools.cs` (context Editor) and `Packages/src/Runtime/PausePoints/UloopPausePointEntry.cs` (context Runtime) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `f5f4e339` feat: gate pause-point hits with the hit-when condition (#2405); `d1e3c21f` feat: report method entry counts for expired pause points (#2402); `779c32b5` feat: add a max-caller-frames option to enable-pause-point — run `git show` on any of them.
AX8 · Test isolation · Production project references a test project · ×4
  • Production project references a test project: UnityCLILoop.Dev → UnityCLILoop.FirstPartyTools.RunTests.Editor — `UnityCLILoop.Dev` (production) references the test project `UnityCLILoop.FirstPartyTools.RunTests.Editor`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: UnityCLILoop.Dev → UnityCLILoop.FirstPartyTools.RunTests.TestFramework.Editor — `UnityCLILoop.Dev` (production) references the test project `UnityCLILoop.FirstPartyTools.RunTests.TestFramework.Editor`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: UnityCLILoop.FirstPartyTools.Editor → UnityCLILoop.FirstPartyTools.RunTests.Editor — `UnityCLILoop.FirstPartyTools.Editor` (production) references the test project `UnityCLILoop.FirstPartyTools.RunTests.Editor`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: UnityCLILoop.FirstPartyTools.Editor → UnityCLILoop.FirstPartyTools.RunTests.TestFramework.Editor — `UnityCLILoop.FirstPartyTools.Editor` (production) references the test project `UnityCLILoop.FirstPartyTools.RunTests.TestFramework.Editor`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 272 finding(s)
SC1 · Supply-chain hygiene · NuGet dependencies are not locked · ×10
  • NuGet dependencies are not locked Directory.Build.props:13 — Directory.Build.props declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/CompileCheckWorker.UnitTests/CompileCheckWorker.UnitTests.csproj:16 — tests/CompileCheckWorker.UnitTests/CompileCheckWorker.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/DynamicCodeExecutionScheduler.UnitTests/DynamicCodeExecutionScheduler.UnitTests.csproj:11 — tests/DynamicCodeExecutionScheduler.UnitTests/DynamicCodeExecutionScheduler.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/OutputFileRetention.UnitTests/OutputFileRetention.UnitTests.csproj:11 — tests/OutputFileRetention.UnitTests/OutputFileRetention.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/RunTestsExecutionTimeout.UnitTests/RunTestsExecutionTimeout.UnitTests.csproj:11 — tests/RunTestsExecutionTimeout.UnitTests/RunTestsExecutionTimeout.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/SharedRoslynCompilerWorker.UnitTests/SharedRoslynCompilerWorker.UnitTests.csproj:11 — tests/SharedRoslynCompilerWorker.UnitTests/SharedRoslynCompilerWorker.UnitTests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/UnityCliLoop.CodeComplexity.Tests/UnityCliLoop.CodeComplexity.Tests.csproj:11 — tests/UnityCliLoop.CodeComplexity.Tests/UnityCliLoop.CodeComplexity.Tests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tests/UnityCliLoop.DeadCodeScanner.Tests/UnityCliLoop.DeadCodeScanner.Tests.csproj:11 — tests/UnityCliLoop.DeadCodeScanner.Tests/UnityCliLoop.DeadCodeScanner.Tests.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tools/UnityCliLoop.CodeComplexity/UnityCliLoop.CodeComplexity.csproj:11 — tools/UnityCliLoop.CodeComplexity/UnityCliLoop.CodeComplexity.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
  • NuGet dependencies are not locked tools/UnityCliLoop.DeadCodeScanner/UnityCliLoop.DeadCodeScanner.csproj:11 — tools/UnityCliLoop.DeadCodeScanner/UnityCliLoop.DeadCodeScanner.csproj declares NuGet packages that no committed packages.lock.json resolves and no central package management pins — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
D3 · God Classes · MethodTooLong · ×9
  • MethodTooLong: CompiledAssemblyBuilder.BuildAsync Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/CompiledAssemblyBuilder.cs:74 — MethodTooLong — BuildAsync runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: HotReloadPatchTargetSupport.ResolvePatchTarget Packages/src/Editor/FirstPartyTools/HotReload/HotReloadPatchTargetSupport.cs:24 — MethodTooLong — ResolvePatchTarget runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× 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: HotReloadOrchestrator.RunAsync Packages/src/Editor/FirstPartyTools/HotReload/HotReloadOrchestrator.cs:76 — MethodTooLong — RunAsync runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UnityCliLoopApplicationRegistration.Register Packages/src/Editor/CompositionRoot/UnityCliLoopApplicationRegistration.cs:17 — MethodTooLong — Register runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ScreenshotUseCase.CaptureWindowsAsync Packages/src/Editor/FirstPartyTools/Screenshot/ScreenshotUseCase.cs:418 — MethodTooLong — CaptureWindowsAsync runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× 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: HotReloadApplyResponseBuilder.Build Packages/src/Editor/FirstPartyTools/HotReload/HotReloadApplyResponseBuilder.cs:16 — MethodTooLong — Build runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SourcePausePointShimResolver.Resolve Packages/src/Editor/FirstPartyTools/PausePoint/SourcePausePointShimResolver.cs:20 — MethodTooLong — Resolve runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ThirdPartyToolMigrationFastSourceTargetDetector.ContainsFastCSharpSourceMigrationTargetAsync Packages/src/Editor/Infrastructure/ThirdPartyToolMigration/ThirdPartyToolMigrationFastSourceTargetDetector.cs:28 — MethodTooLong — ContainsFastCSharpSourceMigrationTargetAsync runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: HotReloadShimIsolation.RunIsolationRetryAsync Packages/src/Editor/FirstPartyTools/HotReload/HotReloadShimIsolation.cs:103 — MethodTooLong — RunIsolationRetryAsync runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×7
  • Edited copy of a member (14 corresponding lines) cli/common/unityprocess/unitydialog/inspect.go:113 — cli/common/unityprocess/unitydialog/inspect.go:113-126 | cli/common/unityprocess/unitydialog/win32.go:12-25 — 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) cli/release-automation/cmd/check-ipc-protocol-reminder/main.go:11 — cli/release-automation/cmd/check-ipc-protocol-reminder/main.go:11-25 | cli/release-automation/cmd/check-release-triggers/main.go:11-24 — 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) cli/dispatcher/internal/dispatcher/dispatcher_freshness.go:216 — cli/dispatcher/internal/dispatcher/dispatcher_freshness.go:216-229 | cli/dispatcher/internal/dispatcher/dispatcher_freshness.go:254-267 — 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) cli/dispatcher/internal/dispatcher/launch_ready.go:76 — cli/dispatcher/internal/dispatcher/launch_ready.go:76-89 | cli/dispatcher/internal/dispatcher/launch_ready.go:126-142 — 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) cli/project-runner/internal/projectrunner/debug_timing.go:50 — cli/project-runner/internal/projectrunner/debug_timing.go:50-67 | cli/project-runner/internal/projectrunner/dynamic_code_wait.go:146-159 — 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) cli/dispatcher/internal/dispatcher/launch_lockfile_probe_unix.go:14 — cli/dispatcher/internal/dispatcher/launch_lockfile_probe_unix.go:14-28 | cli/dispatcher/internal/compilecheck/fastcheck/bootstrap.go:311-324 — 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) cli/common/errors/error_envelope.go:323 — cli/common/errors/error_envelope.go:323-336 | cli/common/errors/error_envelope_classification.go:175-189 — 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 (8 corresponding lines) · ×7
  • Edited copy of a member (8 corresponding lines) cli/dispatcher/internal/install/command.go:81 — cli/dispatcher/internal/install/command.go:81-88 | cli/dispatcher/internal/uninstall/command.go:98-105 — 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) cli/release-automation/internal/automation/publish_coverage_trend.go:45 — cli/release-automation/internal/automation/publish_coverage_trend.go:45-55 | cli/release-automation/internal/automation/unity_package_release_create.go:70-77 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) cli/release-automation/internal/automation/coverage_report.go:341 — cli/release-automation/internal/automation/coverage_report.go:341-354 | cli/release-automation/internal/automation/coverage_report_csharp.go:227-234 — 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) cli/common/clicore/command_registry.go:111 — cli/common/clicore/command_registry.go:111-118 | cli/project-runner/internal/projectrunner/pause_point_unknown_option.go:94-105 — 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) cli/dispatcher/internal/compilecheck/source_set.go:396 — cli/dispatcher/internal/compilecheck/source_set.go:396-403 | cli/dispatcher/internal/dispatcher/skills_dispatch.go:173-183 — 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) cli/project-runner/internal/projectrunner/pause_point_status_options.go:100 — cli/project-runner/internal/projectrunner/pause_point_status_options.go:100-109 | cli/project-runner/internal/projectrunner/pause_point_wait_options.go:78-85 — 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) scripts/smoke-compile-get-logs.py:16 — scripts/smoke-compile-get-logs.py:16-23 | scripts/smoke-uloop-launch.py:15-22 — 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
PF3 · Async & latency hygiene · Sync-over-async blocking · ×6
  • Sync-over-async blocking — 5 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/SharedRoslynCompilerWorkerAssemblyBuilder.cs:130 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/SharedRoslynCompilerWorkerAssemblyBuilder.cs:131 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking Packages/src/Editor/FirstPartyTools/HotReload/Shared/HotReloadSourceSnapshotCapture.cs:194 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking Packages/src/Editor/FirstPartyTools/HotReload/Shared/TransformWorkerServeProtocol.cs:248 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
  • Sync-over-async blocking Packages/src/Editor/FirstPartyTools/HotReload/Shared/TransformWorkerServeProtocol.cs:256 — `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
D3 · God Classes · TooManyMethods · ×5
  • TooManyMethods: HotReloadFileGeneration Packages/src/Editor/FirstPartyTools/HotReload/Patching/HotReloadFileGeneration.cs — TooManyMethods — 280 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ThirdPartyToolMigrationWizardWindow Packages/src/Editor/Presentation/Setup/ThirdPartyToolMigrationWizardWindow.cs — TooManyMethods — 232 significant lines (blank, comment-only and punctuation-only lines excluded), 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.
  • TooManyMethods: SetupWizardWindow Packages/src/Editor/Presentation/Setup/SetupWizardWindow.cs — TooManyMethods — 288 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: HotReloadDomain Packages/src/Editor/FirstPartyTools/HotReload/Patching/HotReloadDomain.cs — TooManyMethods — 263 significant lines (blank, comment-only and punctuation-only lines excluded), 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: UnityCliLoopSettingsWindow Packages/src/Editor/Presentation/UnityCliLoopSettingsWindow.cs — TooManyMethods — 252 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×5
  • Edited copy of a member (16 corresponding lines) cli/common/skillscan/sources.go:65 — cli/common/skillscan/sources.go:65-80 | cli/dispatcher/internal/dispatcher/skills_discovery.go:60-79 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) cli/dispatcher/internal/compilecheck/fastcheck/bootstrap.go:287 — cli/dispatcher/internal/compilecheck/fastcheck/bootstrap.go:287-302 | cli/dispatcher/internal/compilecheck/plan.go:152-170 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) cli/project-runner/internal/projectrunner/pause_point_trigger.go:62 — cli/project-runner/internal/projectrunner/pause_point_trigger.go:62-83 | cli/project-runner/internal/projectrunner/pause_point_trigger_dialog_block.go:79-94 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) cli/project-runner/internal/projectrunner/compile_wait_log.go:28 — cli/project-runner/internal/projectrunner/compile_wait_log.go:28-43 | cli/project-runner/internal/projectrunner/plain_tool_log.go:35-52 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) cli/dispatcher/internal/dispatcher/compile_check.go:342 — cli/dispatcher/internal/dispatcher/compile_check.go:342-357 | cli/dispatcher/internal/dispatcher/launch.go:81-96 — 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 (11 corresponding lines) · ×5
  • Edited copy of a member (11 corresponding lines) cli/release-automation/cmd/stamp-dispatcher-pin/main.go:43 — cli/release-automation/cmd/stamp-dispatcher-pin/main.go:43-54 | cli/release-automation/internal/automation/dispatcher_pin_push.go:231-241 — 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) cli/project-runner/internal/projectrunner/record_video_extract.go:124 — cli/project-runner/internal/projectrunner/record_video_extract.go:124-137 | cli/project-runner/internal/projectrunner/record_video_one_shot.go:289-299 — 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) cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go:323 — cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go:323-337 | cli/project-runner/internal/projectrunner/hot_reload_compile_fallback.go:154-164 — 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) cli/dispatcher/internal/dispatcher/launch_editor_version_error.go:10 — cli/dispatcher/internal/dispatcher/launch_editor_version_error.go:10-20 | cli/dispatcher/internal/dispatcher/launch_log_file.go:101-111 — 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) cli/dispatcher/internal/compilecheck/resultstore/baseline.go:226 — cli/dispatcher/internal/compilecheck/resultstore/baseline.go:226-238 | cli/project-runner/internal/projectrunner/pause_point_trigger.go:220-230 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×5
  • Edited copy of a member (9 corresponding lines) cli/dispatcher/internal/dispatcher/launch_ready.go:196 — cli/dispatcher/internal/dispatcher/launch_ready.go:196-204 | cli/project-runner/internal/projectrunner/dialog_command.go:349-358 — 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) cli/project-runner/internal/projectrunner/early_dialog_report.go:204 — cli/project-runner/internal/projectrunner/early_dialog_report.go:204-212 | cli/project-runner/internal/projectrunner/pause_point_ipc.go:16-26 — 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) cli/common/unityprocess/unitydialog/inspect.go:231 — cli/common/unityprocess/unitydialog/inspect.go:231-239 | cli/common/unityprocess/unitydialog/win32.go:257-266 — 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) cli/project-runner/internal/projectrunner/pause_point_file_line_id.go:26 — cli/project-runner/internal/projectrunner/pause_point_file_line_id.go:26-34 | cli/project-runner/internal/projectrunner/pause_point_wait_options.go:59-67 — 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) cli/dispatcher/internal/compilecheck/assembly_reference.go:64 — cli/dispatcher/internal/compilecheck/assembly_reference.go:64-73 | cli/dispatcher/internal/compilecheck/input_key_identity.go:105-113 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×5
  • Duplicated block (10 lines × 2) cli/dispatcher/internal/dispatcher/dispatcher_periodic_update.go:172 — cli/dispatcher/internal/dispatcher/dispatcher_periodic_update.go:172-181 | cli/dispatcher/internal/dispatcher/dispatcher_required_update.go:41-50 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (10 lines × 2) cli/release-automation/internal/automation/contract_file_at_ref.go:131 — cli/release-automation/internal/automation/contract_file_at_ref.go:131-143 | cli/release-automation/internal/automation/contract_file_at_ref.go:157-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cli/release-automation/internal/automation/contract_file_at_ref.go:131` 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 (10 lines × 2) cli/release-automation/internal/automation/contract_file_at_ref.go:198 — cli/release-automation/internal/automation/contract_file_at_ref.go:198-207 | cli/release-automation/internal/automation/release_pr_checks.go:423-432 — 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 `cli/release-automation/internal/automation/contract_file_at_ref.go:198` 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.
  • Duplicated block (10 lines × 2) cli/project-runner/internal/projectrunner/pause_point_release_recovery.go:144 — cli/project-runner/internal/projectrunner/pause_point_release_recovery.go:144-153 | cli/release-automation/internal/automation/release_pr_checks.go:30-40 — 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 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. Check import visibility before settling on that home: `cli/project-runner/internal/projectrunner/pause_point_release_recovery.go`, `cli/release-automation/internal/automation/release_pr_checks.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.
  • Duplicated block (10 lines × 2) cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go:291 — cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go:291-300 | cli/project-runner/internal/projectrunner/record_video_one_shot.go:269-278 — 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. 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 lines × 2) · ×5
  • Duplicated block (8 lines × 2) cli/dispatcher/internal/dispatcher/skills.go:247 — cli/dispatcher/internal/dispatcher/skills.go:247-254 | cli/dispatcher/internal/dispatcher/skills_v3_migration.go:19-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cli/dispatcher/internal/dispatcher/skills.go:256` calls `WriteFormat` and `cli/dispatcher/internal/dispatcher/skills_v3_migration.go:27` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) cli/dispatcher/internal/dispatcher/skills_dir_status.go:291 — cli/dispatcher/internal/dispatcher/skills_dir_status.go:291-298 | cli/dispatcher/internal/dispatcher/skills_dir_status.go:321-328 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cli/dispatcher/internal/dispatcher/skills_dir_status.go:291` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `cli/dispatcher/internal/dispatcher/skills_dir_status.go:329` calls `Type`, `IsRegular`, `Errorf` and `cli/dispatcher/internal/dispatcher/skills_dir_status.go:299` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) cli/release-automation/internal/automation/dispatcher_pin_freshness.go:217 — cli/release-automation/internal/automation/dispatcher_pin_freshness.go:217-224 | cli/release-automation/internal/automation/dispatcher_pin_stamp.go:220-227 — 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 `cli/release-automation/internal/automation/dispatcher_pin_freshness.go:217` 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 (8 lines × 2) cli/dispatcher/internal/dispatcher/compile_check.go:388 — cli/dispatcher/internal/dispatcher/compile_check.go:388-396 | cli/dispatcher/internal/dispatcher/launch_options.go:111-118 — 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 `cli/dispatcher/internal/dispatcher/compile_check.go:388` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) cli/dispatcher/internal/nativepath/path.go:89 — cli/dispatcher/internal/nativepath/path.go:89-96 | cli/dispatcher/internal/nativepath/path.go:121-128 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cli/dispatcher/internal/nativepath/path.go:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: SetupWizardWindow.cs ↔ CliSetupSection.cs Packages/src/Editor/Presentation/Setup/SetupWizardWindow.cs:1 — `Packages/src/Editor/Presentation/Setup/SetupWizardWindow.cs` and `Packages/src/Editor/Presentation/UIToolkit/Components/CliSetupSection.cs` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `0a2b5fc3` fix: Unity no longer installs a duplicate CLI over a Homebrew-managed…; `bae3a4a2` feat: Unify skills setup UI into a shared panel for settings and setu…; `7aa37fda` feat: Show live progress feedback while installing the CLI (#1959) — run `git show` on any of them.
  • Change coupling: pause_point_enable.go ↔ pause_point_types.go cli/project-runner/internal/projectrunner/pause_point_enable.go:1 — `cli/project-runner/internal/projectrunner/pause_point_enable.go` and `cli/project-runner/internal/projectrunner/pause_point_types.go` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c8e1fe63` fix(pause-point): carry every warning in Warnings and point Message a…; `ea30b1e2` feat: report the line resolution basis in enable-pause-point response…; `7332b030` feat: echo enable-time resolved marker fields on expired pause-point … — run `git show` on any of them.
  • Change coupling: CliSetupSection.cs ↔ UnityCliLoopSettingsWindow.cs Packages/src/Editor/Presentation/UIToolkit/Components/CliSetupSection.cs:1 — `Packages/src/Editor/Presentation/UIToolkit/Components/CliSetupSection.cs` and `Packages/src/Editor/Presentation/UnityCliLoopSettingsWindow.cs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `bae3a4a2` feat: Unify skills setup UI into a shared panel for settings and setu…; `563a9f4d` chore: Consolidate CLI setup action decisions; `0a7fd774` fix: Setup now shows CLI update prompts for outdated CLI installs (#1… — run `git show` on any of them.
  • Change coupling: CompileController.cs ↔ CompileUseCase.cs Packages/src/Editor/FirstPartyTools/Compile/CompileController.cs:1 — `Packages/src/Editor/FirstPartyTools/Compile/CompileController.cs` and `Packages/src/Editor/FirstPartyTools/Compile/CompileUseCase.cs` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `5b8d65eb` feat: warn in the compile response when the compile stops an active P…; `e74a6d84` chore: Avoid duplicate compile result persistence; `b7a95f94` chore: Split compile response persistence responsibilities — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×4
  • Edited copy of a member (27 corresponding lines) cli/common/clicore/global_args.go:11 — cli/common/clicore/global_args.go:11-37 | cli/project-runner/internal/projectrunner/dynamic_code_file.go:18-47 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) cli/release-automation/internal/automation/protocol_minimum_version_guard.go:139 — cli/release-automation/internal/automation/protocol_minimum_version_guard.go:139-169 | cli/release-automation/internal/automation/release_trigger_guard.go:89-115 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) cli/common/project/project.go:159 — cli/common/project/project.go:159-188 | cli/common/skillscan/packages.go:37-63 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) tools/UnityCliLoop.CodeComplexity/CodeComplexityReporter.cs:34 — tools/UnityCliLoop.CodeComplexity/CodeComplexityReporter.cs:34-60 | tools/UnityCliLoop.DeadCodeScanner/DeadCodeReporter.cs:34-63 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×4
  • Edited copy of a member (20 corresponding lines) cli/common/tooldocs/tool_option_help.go:46 — cli/common/tooldocs/tool_option_help.go:46-71 | cli/project-runner/internal/projectrunner/list_output.go:100-119 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) cli/dispatcher/internal/compilecheck/assembly_reference.go:20 — cli/dispatcher/internal/compilecheck/assembly_reference.go:20-39 | cli/release-automation/internal/automation/skill_size.go:45-68 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) cli/common/project/project.go:94 — cli/common/project/project.go:94-113 | cli/common/project/project.go:120-139 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) cli/project-runner/internal/projectrunner/plain_tool_log.go:62 — cli/project-runner/internal/projectrunner/plain_tool_log.go:62-81 | cli/project-runner/internal/projectrunner/plain_tool_log.go:90-112 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×4
  • Edited copy of a member (18 corresponding lines) cli/common/skillscan/packages.go:123 — cli/common/skillscan/packages.go:123-140 | cli/common/skillscan/packages.go:202-221 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) cli/dispatcher/internal/dispatcher/compile_check.go:116 — cli/dispatcher/internal/dispatcher/compile_check.go:116-133 | cli/dispatcher/internal/dispatcher/launch.go:62-79 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) cli/release-automation/internal/automation/release_pr_checks.go:161 — cli/release-automation/internal/automation/release_pr_checks.go:161-178 | cli/release-automation/internal/automation/release_pr_checks.go:240-269 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) cli/common/version/compare.go:144 — cli/common/version/compare.go:144-161 | cli/project-runner/internal/projectrunner/compile_wait.go:169-186 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×4
  • Edited copy of a member (12 corresponding lines) cli/release-automation/internal/automation/contract_file_at_ref.go:195 — cli/release-automation/internal/automation/contract_file_at_ref.go:195-207 | cli/release-automation/internal/automation/release_pr_checks.go:421-432 — 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) cli/dispatcher/attestation/verifier.go:188 — cli/dispatcher/attestation/verifier.go:188-199 | cli/dispatcher/attestation/verifier.go:225-239 — 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) cli/project-runner/internal/projectrunner/control_play_mode_wait.go:228 — cli/project-runner/internal/projectrunner/control_play_mode_wait.go:228-245 | cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go:247-258 — 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) cli/common/unityprocess/lsappinfo_output.go:16 — cli/common/unityprocess/lsappinfo_output.go:16-27 | cli/common/unityprocess/lsappinfo_output.go:29-40 — 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 (7 corresponding lines) · ×4
  • Edited copy of a member (7 corresponding lines) cli/project-runner/internal/projectrunner/compile_wait.go:161 — cli/project-runner/internal/projectrunner/compile_wait.go:161-167 | cli/project-runner/internal/projectrunner/run_tests_domain_reload_wait.go:99-105 — 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) cli/dispatcher/internal/dispatcher/install.go:163 — cli/dispatcher/internal/dispatcher/install.go:163-169 | cli/dispatcher/internal/dispatcher/uninstall.go:102-108 — 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) cli/common/skillscan/packages.go:355 — cli/common/skillscan/packages.go:355-361 | cli/dispatcher/internal/dispatcher/dispatcher_periodic_update.go:57-63 — 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) tools/UnityCliLoop.CodeComplexity/CodeComplexityAnalyzerRunner.cs:161 — tools/UnityCliLoop.CodeComplexity/CodeComplexityAnalyzerRunner.cs:161-173 | tools/UnityCliLoop.CodeComplexity/ConfigureAwaitGuard.cs:193-199 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×4
  • Duplicated block (11 lines × 2) cli/dispatcher/attestation/verifier.go:189 — cli/dispatcher/attestation/verifier.go:189-199 | cli/dispatcher/attestation/verifier.go:229-239 — 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 `cli/dispatcher/attestation/verifier.go:229` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cli/dispatcher/attestation/verifier.go:227` calls `Errorf` and `cli/dispatcher/attestation/verifier.go:188` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) cli/release-automation/internal/automation/dispatcher_pin_guard.go:112 — cli/release-automation/internal/automation/dispatcher_pin_guard.go:112-122 | cli/release-automation/internal/automation/dispatcher_pin_stamp.go:88-98 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) cli/common/tooldocs/tool_option_help.go:143 — cli/common/tooldocs/tool_option_help.go:143-153 | cli/common/tooldocs/tool_options.go:57-67 — 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 (11 lines × 2) cli/project-runner/internal/projectrunner/run.go:386 — cli/project-runner/internal/projectrunner/run.go:386-396 | cli/project-runner/internal/projectrunner/run.go:417-427 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `cli/project-runner/internal/projectrunner/run.go:386` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cli/project-runner/internal/projectrunner/run.go:415` calls `runSync` and `cli/project-runner/internal/projectrunner/run.go:383` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) cli/dispatcher/internal/install/command.go:82 — cli/dispatcher/internal/install/command.go:82-88 | cli/dispatcher/internal/uninstall/command.go:99-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) cli/common/vibelog/cli_vibe.go:81 — cli/common/vibelog/cli_vibe.go:81-87 | cli/project-runner/internal/projectrunner/debug_timing.go:83-89 — 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. Check import visibility before settling on that home: `cli/project-runner/internal/projectrunner/debug_timing.go` sits under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.
  • Duplicated block (7 lines × 2) cli/release-automation/internal/automation/dispatcher_pin_freshness.go:210 — cli/release-automation/internal/automation/dispatcher_pin_freshness.go:210-216 | cli/release-automation/internal/automation/dispatcher_pin_stamp.go:212-218 — 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 `cli/release-automation/internal/automation/dispatcher_pin_freshness.go:210` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) cli/project-runner/internal/projectrunner/compile_attach.go:321 — cli/project-runner/internal/projectrunner/compile_attach.go:321-326 | cli/project-runner/internal/projectrunner/compile_wait.go:262-267 — 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 `cli/project-runner/internal/projectrunner/compile_attach.go:321` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) cli/dispatcher/internal/dispatcher/compile_check.go:202 — cli/dispatcher/internal/dispatcher/compile_check.go:202-208 | cli/dispatcher/internal/dispatcher/launch.go:446-451 — 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) cli/release-automation/cmd/check-dispatcher-pin-freshness/main.go:13 — cli/release-automation/cmd/check-dispatcher-pin-freshness/main.go:13-18 | cli/release-automation/cmd/check-release-please-gate/main.go:13-18 — 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.
D5 · Coupling · Off the main sequence · ×3
  • Off the main sequence: Unity.InternalAPIEditorBridge.024 — Unity.InternalAPIEditorBridge.024: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
  • Off the main sequence: UnityCLILoop.PausePoints.Runtime — UnityCLILoop.PausePoints.Runtime: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
  • Off the main sequence: UnityCLILoop.Domain — UnityCLILoop.Domain: abstractness 0.12, instability 0.13, distance 0.76 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×2
  • Edited copy of a member (32 corresponding lines) cli/release-automation/internal/automation/dispatcher_pin_freshness.go:201 — cli/release-automation/internal/automation/dispatcher_pin_freshness.go:201-232 | cli/release-automation/internal/automation/dispatcher_pin_stamp.go:204-237 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (32 corresponding lines) cli/common/unityprocess/process_darwin.go:16 — cli/common/unityprocess/process_darwin.go:16-47 | cli/common/unityprocess/process_linux.go:18-53 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×2
  • Edited copy of a member (33 corresponding lines) cli/common/errors/command_suggestions.go:48 — cli/common/errors/command_suggestions.go:48-80 | cli/project-runner/internal/projectrunner/tool_param_suggestions.go:248-280 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) cli/release-automation/internal/automation/dispatcher_pin_guard.go:94 — cli/release-automation/internal/automation/dispatcher_pin_guard.go:94-127 | cli/release-automation/internal/automation/dispatcher_pin_stamp.go:68-100 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×2
  • Edited copy of a member (21 corresponding lines) cli/release-automation/internal/automation/publish_coverage_trend.go:57 — cli/release-automation/internal/automation/publish_coverage_trend.go:57-77 | cli/release-automation/internal/automation/unity_package_release_plan.go:67-96 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (21 corresponding lines) cli/release-automation/internal/automation/file_length.go:62 — cli/release-automation/internal/automation/file_length.go:62-86 | cli/release-automation/internal/automation/skill_size.go:73-93 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×2
  • Edited copy of a member (17 corresponding lines) cli/release-automation/internal/automation/published_release.go:26 — cli/release-automation/internal/automation/published_release.go:26-42 | cli/release-automation/internal/automation/unity_package_release_create.go:281-297 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) cli/dispatcher/internal/dispatcher/dispatcher_v2_detect.go:263 — cli/dispatcher/internal/dispatcher/dispatcher_v2_detect.go:263-279 | cli/dispatcher/internal/dispatcher/dispatcher_v2_detect.go:374-393 — 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 copy of a member (19 corresponding lines) · ×2
  • Edited copy of a member (19 corresponding lines) cli/release-automation/internal/automation/protocol_minimum_version_comment.go:237 — cli/release-automation/internal/automation/protocol_minimum_version_comment.go:237-256 | cli/release-automation/internal/automation/pull_request_checks.go:39-57 — 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) cli/release-automation/internal/automation/file_length_sloc.go:206 — cli/release-automation/internal/automation/file_length_sloc.go:206-224 | cli/release-automation/internal/automation/file_length_sloc.go:226-244 — 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 (13 corresponding lines) · ×2
  • Edited copy of a member (13 corresponding lines) cli/dispatcher/internal/dispatcher/launch.go:245 — cli/dispatcher/internal/dispatcher/launch.go:245-257 | cli/dispatcher/internal/dispatcher/launch_v2_server_ready.go:219-234 — 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) tools/UnityCliLoop.DeadCodeScanner/UnityKeeperClassifier.cs:136 — tools/UnityCliLoop.DeadCodeScanner/UnityKeeperClassifier.cs:136-152 | tools/UnityCliLoop.DeadCodeScanner/UnityKeeperClassifier.cs:207-219 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 19+ corresponding lines) cli/project-runner/internal/projectrunner/pause_point_ipc.go:33 — cli/project-runner/internal/projectrunner/pause_point_ipc.go:33-52 | cli/project-runner/internal/projectrunner/pause_point_ipc.go:65-83 | cli/project-runner/internal/projectrunner/run_tests_domain_reload_wait.go:118-136 — 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.
  • Edited copies of one member (3 members, 19+ corresponding lines) cli/project-runner/internal/projectrunner/list_output.go:180 — cli/project-runner/internal/projectrunner/list_output.go:180-198 | cli/project-runner/internal/projectrunner/list_output.go:202-220 | cli/project-runner/internal/projectrunner/list_output.go:224-242 — 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 copies of one member (3 members, 15+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 15+ corresponding lines) cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go:289 — cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go:289-303 | cli/project-runner/internal/projectrunner/record_video_one_shot.go:267-281 | cli/project-runner/internal/projectrunner/run_tests_implicit_compile.go:100-118 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 15+ corresponding lines) cli/project-runner/internal/projectrunner/compile_wait_log.go:221 — cli/project-runner/internal/projectrunner/compile_wait_log.go:221-236 | cli/project-runner/internal/projectrunner/compile_wait_log.go:245-260 | cli/project-runner/internal/projectrunner/compile_wait_log.go:270-284 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×2
  • Edited copy of a member (4 corresponding lines) cli/release-automation/internal/automation/package_release_pr_ready_merge.go:210 — cli/release-automation/internal/automation/package_release_pr_ready_merge.go:210-213 | cli/release-automation/internal/automation/release_pr_checks.go:341-344 — 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) scripts/smoke-compile-get-logs.py:73 — scripts/smoke-compile-get-logs.py:73-77 | scripts/smoke-uloop-launch.py:175-178 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) cli/dispatcher/internal/dispatcher/package.go:147 — cli/dispatcher/internal/dispatcher/package.go:147-162 | cli/dispatcher/internal/dispatcher/package.go:201-216 — 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 `cli/dispatcher/internal/dispatcher/package.go:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (16 lines × 2) cli/dispatcher/internal/dispatcher/skills_dir_status.go:299 — cli/dispatcher/internal/dispatcher/skills_dir_status.go:299-314 | cli/dispatcher/internal/dispatcher/skills_dir_status.go:332-347 — 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 `cli/dispatcher/internal/dispatcher/skills_dir_status.go:299` 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 (13 lines × 2) · ×2
  • Duplicated block (13 lines × 2) cli/dispatcher/internal/compilecheck/result_cache.go:150 — cli/dispatcher/internal/compilecheck/result_cache.go:150-162 | cli/dispatcher/internal/compilecheck/resultstore/store.go:125-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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) cli/dispatcher/internal/dispatcher/skills_dir_cleanup.go:79 — cli/dispatcher/internal/dispatcher/skills_dir_cleanup.go:79-91 | cli/dispatcher/internal/dispatcher/skills_targets.go:158-170 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2
  • Duplicated block (9 lines × 2) cli/dispatcher/internal/compilecheck/assembly_set.go:52 — cli/dispatcher/internal/compilecheck/assembly_set.go:52-61 | cli/dispatcher/internal/compilecheck/predefined_sources.go:99-107 — 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 `cli/dispatcher/internal/compilecheck/assembly_set.go:52` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) cli/project-runner/internal/projectrunner/dynamic_code_wait.go:61 — cli/project-runner/internal/projectrunner/dynamic_code_wait.go:61-69 | cli/project-runner/internal/projectrunner/dynamic_code_wait.go:88-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×2
  • Duplicated block (13 lines × 3) cli/common/tooldocs/pause_point_cli_options.go:218 — cli/common/tooldocs/pause_point_cli_options.go:218-230 | cli/common/tooldocs/pause_point_cli_options.go:235-247 | cli/common/tooldocs/record_video_cli_options.go:64-76 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `cli/common/tooldocs/pause_point_cli_options.go:218` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (13 lines × 3) tools/UnityCliLoop.CodeComplexity/CodeComplexityAnalyzerRunner.cs:121 — tools/UnityCliLoop.CodeComplexity/CodeComplexityAnalyzerRunner.cs:121-133 | tools/UnityCliLoop.CodeComplexity/ConfigureAwaitGuard.cs:178-190 | tools/UnityCliLoop.DeadCodeScanner/AsmdefWorkspaceBuilder.cs:309-321 — 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. 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • Low cohesion: user32API (LCOM4 7) cli/common/unityprocess/focus_windows_user32.go:15 — user32API's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: ExecuteDynamicCodeResponse (LCOM4 5) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/ExecuteDynamicCodeResponse.cs:13 — ExecuteDynamicCodeResponse'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.
D1 · Cyclomatic Complexity · CommandLineOptions.TryParse (cyclomatic 19) · ×1
  • CommandLineOptions.TryParse (cyclomatic 19) tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs:31 — CommandLineOptions.TryParse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AwaitableHelper.ConvertValueTaskToTask (cyclomatic 16) · ×1
  • AwaitableHelper.ConvertValueTaskToTask (cyclomatic 16) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/Execution/AwaitableHelper.cs:327 — AwaitableHelper.ConvertValueTaskToTask has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. 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. This shape REPEATS in the file: one other method here (AwaitableHelper.ConvertGenericValueTaskToTask) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · AwaitableHelper.ConvertGenericValueTaskToTask (cyclomatic 16) · ×1
  • AwaitableHelper.ConvertGenericValueTaskToTask (cyclomatic 16) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/Execution/AwaitableHelper.cs:428 — AwaitableHelper.ConvertGenericValueTaskToTask has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. 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. This shape REPEATS in the file: one other method here (AwaitableHelper.ConvertValueTaskToTask) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D10 · Test Quality · Fixed-sleep synchronisation · ×1
  • Fixed-sleep synchronisation: ReadLineAsync_WhenCanceledDuringWait_ShouldThrowAndAllowPipeClose tests/SharedRoslynCompilerWorker.UnitTests/SharedRoslynCompilerWorkerLineReaderTests.cs:67 — This test starts a background task and then orders itself against it with `Task.Delay(20)` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
D2 · Cognitive Complexity · CommandLineOptions.TryParse (cognitive 42) · ×1
  • CommandLineOptions.TryParse (cognitive 42) tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs:31 — CommandLineOptions.TryParse has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · projectrunner.buildToolParams (cognitive 30) · ×1
  • projectrunner.buildToolParams (cognitive 30) cli/project-runner/internal/projectrunner/tool_params.go:15 — projectrunner.buildToolParams has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (28 pts), boolean chains 1, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dispatcher.resolveDispatcherLatestReleaseTag (cognitive 29) · ×1
  • dispatcher.resolveDispatcherLatestReleaseTag (cognitive 29) cli/dispatcher/internal/dispatcher/attestation_release.go:57 — dispatcher.resolveDispatcherLatestReleaseTag has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AutoUsingResolver.ResolveAsync (cognitive 26) · ×1
  • AutoUsingResolver.ResolveAsync (cognitive 26) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/AutoUsingResolver.cs:22 — AutoUsingResolver.ResolveAsync has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · projectrunner.waitForControlPlayModeState (cognitive 26) · ×1
  • projectrunner.waitForControlPlayModeState (cognitive 26) cli/project-runner/internal/projectrunner/control_play_mode_wait.go:166 — projectrunner.waitForControlPlayModeState has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (22 pts), match/switch 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 · projectrunner.sendWithTransientConnectionRetryAttempts (cognitive 25) · ×1
  • projectrunner.sendWithTransientConnectionRetryAttempts (cognitive 25) cli/project-runner/internal/projectrunner/connection_retry.go:255 — projectrunner.sendWithTransientConnectionRetryAttempts has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CommandLineOptions.Parse (cognitive 24) · ×1
  • CommandLineOptions.Parse (cognitive 24) tools/UnityCliLoop.DeadCodeScanner/CommandLineOptions.cs:11 — CommandLineOptions.Parse has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PreUsingResolver.ExtractQualifiedTypeIdentifiers (cognitive 24) · ×1
  • PreUsingResolver.ExtractQualifiedTypeIdentifiers (cognitive 24) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/PreUsingResolver.cs:281 — PreUsingResolver.ExtractQualifiedTypeIdentifiers has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HierarchyService.GetRootGameObjects (cognitive 24) · ×1
  • HierarchyService.GetRootGameObjects (cognitive 24) Packages/src/Editor/FirstPartyTools/GetHierarchy/HierarchyAnalyzer/HierarchyService.cs:144 — HierarchyService.GetRootGameObjects has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationInterpolatedStringRules.FindRegularInterpolatedStringEndIndex (cognitive 23) · ×1
  • ThirdPartyToolMigrationInterpolatedStringRules.FindRegularInterpolatedStringEndIndex (cognitive 23) Packages/src/Editor/Domain/ThirdPartyToolMigrationInterpolatedStringRules.cs:10 — ThirdPartyToolMigrationInterpolatedStringRules.FindRegularInterpolatedStringEndIndex has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AssemblyTypeIndex.Build (cognitive 23) · ×1
  • AssemblyTypeIndex.Build (cognitive 23) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/AssemblyTypeIndex.cs:39 — AssemblyTypeIndex.Build has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UnityCliLoopServerRecoveryExecutor.TryBindWithWaitAsync (cognitive 23) · ×1
  • UnityCliLoopServerRecoveryExecutor.TryBindWithWaitAsync (cognitive 23) Packages/src/Editor/Infrastructure/Server/UnityCliLoopServerRecoveryExecutor.cs:142 — UnityCliLoopServerRecoveryExecutor.TryBindWithWaitAsync has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dispatcher.formatJSONRawForEmit (cognitive 23) · ×1
  • dispatcher.formatJSONRawForEmit (cognitive 23) cli/dispatcher/internal/dispatcher/package_manifest_json.go:163 — dispatcher.formatJSONRawForEmit has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DeadCodeScanner.ScanAsync (cognitive 21) · ×1
  • DeadCodeScanner.ScanAsync (cognitive 21) tools/UnityCliLoop.DeadCodeScanner/DeadCodeScanner.cs:20 — DeadCodeScanner.ScanAsync has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AwaitableHelper.ConvertValueTaskToTask (cognitive 21) · ×1
  • AwaitableHelper.ConvertValueTaskToTask (cognitive 21) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/Execution/AwaitableHelper.cs:327 — AwaitableHelper.ConvertValueTaskToTask has cognitive complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to one function literal inside it that branches. 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. This shape REPEATS in the file: one other method here (AwaitableHelper.ConvertGenericValueTaskToTask) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · AwaitableHelper.ConvertGenericValueTaskToTask (cognitive 21) · ×1
  • AwaitableHelper.ConvertGenericValueTaskToTask (cognitive 21) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/Execution/AwaitableHelper.cs:428 — AwaitableHelper.ConvertGenericValueTaskToTask has cognitive complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 belong to one function literal inside it that branches. 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. This shape REPEATS in the file: one other method here (AwaitableHelper.ConvertValueTaskToTask) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · HotReloadCallSiteBackfill.RunAllAsync (cognitive 21) · ×1
  • HotReloadCallSiteBackfill.RunAllAsync (cognitive 21) Packages/src/Editor/FirstPartyTools/HotReload/CompiledCallers/HotReloadCallSiteBackfill.cs:142 — HotReloadCallSiteBackfill.RunAllAsync has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · compilecheck.topologicalOrder (cognitive 21) · ×1
  • compilecheck.topologicalOrder (cognitive 21) cli/dispatcher/internal/compilecheck/plan.go:344 — compilecheck.topologicalOrder has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 6 (8 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationDeclarationNameRules.IsTupleTypeClose (cognitive 20) · ×1
  • ThirdPartyToolMigrationDeclarationNameRules.IsTupleTypeClose (cognitive 20) Packages/src/Editor/Domain/ThirdPartyToolMigrationDeclarationNameRules.cs:252 — ThirdPartyToolMigrationDeclarationNameRules.IsTupleTypeClose has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PlayModeViewRenderWaiter.WaitForRenderedFrameAsync (cognitive 20) · ×1
  • PlayModeViewRenderWaiter.WaitForRenderedFrameAsync (cognitive 20) Packages/src/Editor/FirstPartyTools/Screenshot/PlayModeViewRenderWaiter.cs:45 — PlayModeViewRenderWaiter.WaitForRenderedFrameAsync has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RaycastHitClusterer.SplitIntoConnectedComponents (cognitive 20) · ×1
  • RaycastHitClusterer.SplitIntoConnectedComponents (cognitive 20) Packages/src/Editor/FirstPartyTools/Screenshot/RaycastAnnotation/RaycastHitClusterer.cs:76 — RaycastHitClusterer.SplitIntoConnectedComponents has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UnityCliLoopBridgeServer.ServerLoopAsync (cognitive 20) · ×1
  • UnityCliLoopBridgeServer.ServerLoopAsync (cognitive 20) Packages/src/Editor/Infrastructure/UnityCliLoopBridgeServer.cs:261 — UnityCliLoopBridgeServer.ServerLoopAsync has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · projectrunner.waitForAttachedCompileCompletion (cognitive 20) · ×1
  • projectrunner.waitForAttachedCompileCompletion (cognitive 20) cli/project-runner/internal/projectrunner/compile_attach.go:263 — projectrunner.waitForAttachedCompileCompletion has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 3, match/switch 1 (2 pts), 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 · ThirdPartyToolMigrationTimingDeclarationRules.RemoveLegacyPlayerLoopTimingParametersInCode (cognitive 19) · ×1
  • ThirdPartyToolMigrationTimingDeclarationRules.RemoveLegacyPlayerLoopTimingParametersInCode (cognitive 19) Packages/src/Editor/Domain/ThirdPartyToolMigrationTimingDeclarationRules.cs:52 — ThirdPartyToolMigrationTimingDeclarationRules.RemoveLegacyPlayerLoopTimingParametersInCode has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ExternalSceneChangeResolver.ResolveExternalSceneChanges (cognitive 19) · ×1
  • ExternalSceneChangeResolver.ResolveExternalSceneChanges (cognitive 19) Packages/src/Editor/FirstPartyTools/Compile/ExternalSceneChangeResolver.cs:40 — ExternalSceneChangeResolver.ResolveExternalSceneChanges has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HotReloadShimCompileFailureIsolationTrigger.RewriteRetryOnlySkippedReasons (cognitive 19) · ×1
  • HotReloadShimCompileFailureIsolationTrigger.RewriteRetryOnlySkippedReasons (cognitive 19) Packages/src/Editor/FirstPartyTools/HotReload/HotReloadShimCompileFailureIsolationTrigger.cs:17 — HotReloadShimCompileFailureIsolationTrigger.RewriteRetryOnlySkippedReasons has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ScreenshotUseCase.CaptureWindowsAsync (cognitive 19) · ×1
  • ScreenshotUseCase.CaptureWindowsAsync (cognitive 19) Packages/src/Editor/FirstPartyTools/Screenshot/ScreenshotUseCase.cs:418 — ScreenshotUseCase.CaptureWindowsAsync has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationAsmdefTextEditor.FindTopLevelReferencesArray (cognitive 19) · ×1
  • ThirdPartyToolMigrationAsmdefTextEditor.FindTopLevelReferencesArray (cognitive 19) Packages/src/Editor/Infrastructure/ThirdPartyToolMigration/ThirdPartyToolMigrationAsmdefTextEditor.cs:37 — ThirdPartyToolMigrationAsmdefTextEditor.FindTopLevelReferencesArray has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SetupWizardWindowResizer.MeasurePreferredContentWidth (cognitive 19) · ×1
  • SetupWizardWindowResizer.MeasurePreferredContentWidth (cognitive 19) Packages/src/Editor/Presentation/Setup/SetupWizardWindowResizer.cs:95 — SetupWizardWindowResizer.MeasurePreferredContentWidth has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · clicore.waitForToolReadinessWithDeps (cognitive 19) · ×1
  • clicore.waitForToolReadinessWithDeps (cognitive 19) cli/common/clicore/tool_readiness.go:66 — clicore.waitForToolReadinessWithDeps has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 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 · ThirdPartyToolMigrationTimingMethodBodyRules.FindExpressionBodiedMemberSemicolonIndex (cognitive 18) · ×1
  • ThirdPartyToolMigrationTimingMethodBodyRules.FindExpressionBodiedMemberSemicolonIndex (cognitive 18) Packages/src/Editor/Domain/ThirdPartyToolMigrationTimingMethodBodyRules.cs:142 — ThirdPartyToolMigrationTimingMethodBodyRules.FindExpressionBodiedMemberSemicolonIndex has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HotReloadOneShotCallerNoteEnricher.BuildNotes (cognitive 18) · ×1
  • HotReloadOneShotCallerNoteEnricher.BuildNotes (cognitive 18) Packages/src/Editor/FirstPartyTools/HotReload/CompiledCallers/HotReloadOneShotCallerNoteEnricher.cs:77 — HotReloadOneShotCallerNoteEnricher.BuildNotes has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TransformWorkerOutputValidator.TryValidateHomeAssemblyNames (cognitive 18) · ×1
  • TransformWorkerOutputValidator.TryValidateHomeAssemblyNames (cognitive 18) Packages/src/Editor/FirstPartyTools/HotReload/Shared/TransformWorkerOutputValidator.cs:140 — TransformWorkerOutputValidator.TryValidateHomeAssemblyNames has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UnityCliLoopBridgeClientSessionManager.HandleClientAsync (cognitive 18) · ×1
  • UnityCliLoopBridgeClientSessionManager.HandleClientAsync (cognitive 18) Packages/src/Editor/Infrastructure/UnityCliLoopBridgeClientSessionManager.cs:125 — UnityCliLoopBridgeClientSessionManager.HandleClientAsync has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · compilecheck.compileUnits (cognitive 18) · ×1
  • compilecheck.compileUnits (cognitive 18) cli/dispatcher/internal/compilecheck/scheduler.go:109 — compilecheck.compileUnits has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dispatcher.parseInstallOptions (cognitive 18) · ×1
  • dispatcher.parseInstallOptions (cognitive 18) cli/dispatcher/internal/dispatcher/install.go:89 — dispatcher.parseInstallOptions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (16 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 · projectrunner.pollCompileCompletion (cognitive 18) · ×1
  • projectrunner.pollCompileCompletion (cognitive 18) cli/project-runner/internal/projectrunner/compile_wait.go:205 — projectrunner.pollCompileCompletion has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, match/switch 1 (2 pts), 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 · projectrunner.waitForBusyEditor (cognitive 18) · ×1
  • projectrunner.waitForBusyEditor (cognitive 18) cli/project-runner/internal/projectrunner/hot_reload_busy_wait.go:124 — projectrunner.waitForBusyEditor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 2, match/switch 1 (2 pts), 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 · automation.AnalyzeReleaseTriggerGuard (cognitive 18) · ×1
  • automation.AnalyzeReleaseTriggerGuard (cognitive 18) cli/release-automation/internal/automation/release_trigger_guard.go:181 — automation.AnalyzeReleaseTriggerGuard has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 4 (6 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationDeclarationNameRules.FindListOpenParenthesisIndex (cognitive 17) · ×1
  • ThirdPartyToolMigrationDeclarationNameRules.FindListOpenParenthesisIndex (cognitive 17) Packages/src/Editor/Domain/ThirdPartyToolMigrationDeclarationNameRules.cs:164 — ThirdPartyToolMigrationDeclarationNameRules.FindListOpenParenthesisIndex has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ThirdPartyToolMigrationDeclarationNameRules.FindListCloseParenthesisIndex) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · ThirdPartyToolMigrationDeclarationNameRules.FindListCloseParenthesisIndex (cognitive 17) · ×1
  • ThirdPartyToolMigrationDeclarationNameRules.FindListCloseParenthesisIndex (cognitive 17) Packages/src/Editor/Domain/ThirdPartyToolMigrationDeclarationNameRules.cs:198 — ThirdPartyToolMigrationDeclarationNameRules.FindListCloseParenthesisIndex has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ThirdPartyToolMigrationDeclarationNameRules.FindListOpenParenthesisIndex) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · ThirdPartyToolMigrationEditorDelayRules.GetMigratedEditorDelayFrameArguments (cognitive 17) · ×1
  • ThirdPartyToolMigrationEditorDelayRules.GetMigratedEditorDelayFrameArguments (cognitive 17) Packages/src/Editor/Domain/ThirdPartyToolMigrationEditorDelayRules.cs:231 — ThirdPartyToolMigrationEditorDelayRules.GetMigratedEditorDelayFrameArguments has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationTimingMethodBodyRules.FindMethodImplementationUsageRange (cognitive 17) · ×1
  • ThirdPartyToolMigrationTimingMethodBodyRules.FindMethodImplementationUsageRange (cognitive 17) Packages/src/Editor/Domain/ThirdPartyToolMigrationTimingMethodBodyRules.cs:52 — ThirdPartyToolMigrationTimingMethodBodyRules.FindMethodImplementationUsageRange has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TransformWorkerOutputValidator.TryValidatePreparationFile (cognitive 17) · ×1
  • TransformWorkerOutputValidator.TryValidatePreparationFile (cognitive 17) Packages/src/Editor/FirstPartyTools/HotReload/Shared/TransformWorkerOutputValidator.cs:284 — TransformWorkerOutputValidator.TryValidatePreparationFile has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HotReloadWiredValuePersistence.ReportMissingHosts (cognitive 17) · ×1
  • HotReloadWiredValuePersistence.ReportMissingHosts (cognitive 17) Packages/src/Editor/FirstPartyTools/HotReload/WiredValues/HotReloadWiredValuePersistence.cs:280 — HotReloadWiredValuePersistence.ReportMissingHosts has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SourcePausePointResolver.FindNearbyCompiledMethods (cognitive 17) · ×1
  • SourcePausePointResolver.FindNearbyCompiledMethods (cognitive 17) Packages/src/Editor/FirstPartyTools/PausePoint/SourcePausePointResolver.cs:363 — SourcePausePointResolver.FindNearbyCompiledMethods has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FrameParser.TryParseContentLength (cognitive 17) · ×1
  • FrameParser.TryParseContentLength (cognitive 17) Packages/src/Editor/Infrastructure/FrameParser.cs:131 — FrameParser.TryParseContentLength has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationCrossFileTimingMigrationPlanner.ApplyCrossFilePlayerLoopTimingCallerArgumentMigrations (cognitive 17) · ×1
  • ThirdPartyToolMigrationCrossFileTimingMigrationPlanner.ApplyCrossFilePlayerLoopTimingCallerArgumentMigrations (cognitive 17) Packages/src/Editor/Infrastructure/ThirdPartyToolMigration/ThirdPartyToolMigrationCrossFileTimingMigrationPlanner.cs:45 — ThirdPartyToolMigrationCrossFileTimingMigrationPlanner.ApplyCrossFilePlayerLoopTimingCallerArgumentMigrations has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationPreflightScanner.FindMigrationTargetAsync (cognitive 17) · ×1
  • ThirdPartyToolMigrationPreflightScanner.FindMigrationTargetAsync (cognitive 17) Packages/src/Editor/Infrastructure/ThirdPartyToolMigration/ThirdPartyToolMigrationPreflightScanner.cs:45 — ThirdPartyToolMigrationPreflightScanner.FindMigrationTargetAsync has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Compiler.reuseOrCompile (cognitive 17) · ×1
  • Compiler.reuseOrCompile (cognitive 17) cli/dispatcher/internal/compilecheck/result_cache.go:17 — Compiler.reuseOrCompile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 3 (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 · projectrunner.extractPausePointEnableAwaitFlags (cognitive 17) · ×1
  • projectrunner.extractPausePointEnableAwaitFlags (cognitive 17) cli/project-runner/internal/projectrunner/pause_point_enable.go:114 — projectrunner.extractPausePointEnableAwaitFlags has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · automation.buildDispatcherArchiveManifest (cognitive 17) · ×1
  • automation.buildDispatcherArchiveManifest (cognitive 17) cli/release-automation/internal/automation/dispatcher_pin_stamp.go:115 — automation.buildDispatcherArchiveManifest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationApplicationAndFirstPartyTypeReplacementRules.ReplaceLegacyFirstPartyScreenshotTypeNamesInCode (cognitive 16) · ×1
  • ThirdPartyToolMigrationApplicationAndFirstPartyTypeReplacementRules.ReplaceLegacyFirstPartyScreenshotTypeNamesInCode (cognitive 16) Packages/src/Editor/Domain/ThirdPartyToolMigrationApplicationAndFirstPartyTypeReplacementRules.cs:139 — ThirdPartyToolMigrationApplicationAndFirstPartyTypeReplacementRules.ReplaceLegacyFirstPartyScreenshotTypeNamesInCode has cognitive complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThirdPartyToolMigrationCodeTextMaskInterpolationRules.MarkInterpolatedVerbatimStringAsIgnored (cognitive 16) · ×1
  • ThirdPartyToolMigrationCodeTextMaskInterpolationRules.MarkInterpolatedVerbatimStringAsIgnored (cognitive 16) Packages/src/Editor/Domain/ThirdPartyToolMigrationCodeTextMaskInterpolationRules.cs:159 — ThirdPartyToolMigrationCodeTextMaskInterpolationRules.MarkInterpolatedVerbatimStringAsIgnored has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DynamicCodeLiteralHoister.TryHoistIntegerLiteral (cognitive 16) · ×1
  • DynamicCodeLiteralHoister.TryHoistIntegerLiteral (cognitive 16) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/DynamicCodeLiteralHoister.cs:202 — DynamicCodeLiteralHoister.TryHoistIntegerLiteral has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StaticLocalFunctionHeaderScanner.TrySkipReturnTypeAndName (cognitive 16) · ×1
  • StaticLocalFunctionHeaderScanner.TrySkipReturnTypeAndName (cognitive 16) Packages/src/Editor/FirstPartyTools/ExecuteDynamicCode/DynamicCompilation/StaticLocalFunctionHeaderScanner.cs:61 — StaticLocalFunctionHeaderScanner.TrySkipReturnTypeAndName has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HierarchyService.GetSelectedRootGameObjects (cognitive 16) · ×1
  • HierarchyService.GetSelectedRootGameObjects (cognitive 16) Packages/src/Editor/FirstPartyTools/GetHierarchy/HierarchyAnalyzer/HierarchyService.cs:42 — HierarchyService.GetSelectedRootGameObjects has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · HotReloadPatchTargetSupport.ResolvePatchTarget (cognitive 16) · ×1
  • HotReloadPatchTargetSupport.ResolvePatchTarget (cognitive 16) Packages/src/Editor/FirstPartyTools/HotReload/HotReloadPatchTargetSupport.cs:24 — HotReloadPatchTargetSupport.ResolvePatchTarget has cognitive complexity 16 (threshold 15). 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 · SourcePausePointHotReloadRetarget.RetargetMarkersOntoHotReloadPatch (cognitive 16) · ×1
  • SourcePausePointHotReloadRetarget.RetargetMarkersOntoHotReloadPatch (cognitive 16) Packages/src/Editor/FirstPartyTools/PausePoint/SourcePausePointHotReloadRetarget.cs:190 — SourcePausePointHotReloadRetarget.RetargetMarkersOntoHotReloadPatch has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RunTestsNoTestsDiagnosticService.Analyze (cognitive 16) · ×1
  • RunTestsNoTestsDiagnosticService.Analyze (cognitive 16) Packages/src/Editor/FirstPartyTools/RunTests/RunTestsNoTestsDiagnosticService.cs:97 — RunTestsNoTestsDiagnosticService.Analyze has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MouseUiIncrementalDragExecutor.ExecuteDragStart (cognitive 16) · ×1
  • MouseUiIncrementalDragExecutor.ExecuteDragStart (cognitive 16) Packages/src/Editor/FirstPartyTools/SimulateMouseUi/MouseUiIncrementalDragExecutor.cs:18 — MouseUiIncrementalDragExecutor.ExecuteDragStart has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProjectFileInventory.WalkDirectoryTreeAsync (cognitive 16) · ×1
  • ProjectFileInventory.WalkDirectoryTreeAsync (cognitive 16) Packages/src/Editor/Infrastructure/ThirdPartyToolMigration/ThirdPartyToolMigrationProjectFileInventory.cs:137 — ProjectFileInventory.WalkDirectoryTreeAsync has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · unityprocess.splitWindowsCommandLine (cognitive 16) · ×1
  • unityprocess.splitWindowsCommandLine (cognitive 16) cli/common/unityprocess/windows_command_line.go:9 — unityprocess.splitWindowsCommandLine has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, 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 · compilecheck.RebuildSources (cognitive 16) · ×1
  • compilecheck.RebuildSources (cognitive 16) cli/dispatcher/internal/compilecheck/source_set.go:175 — compilecheck.RebuildSources has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · dispatcher.runSkillsDirInstall (cognitive 16) · ×1
  • dispatcher.runSkillsDirInstall (cognitive 16) cli/dispatcher/internal/dispatcher/skills_dir.go:37 — dispatcher.runSkillsDirInstall has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), 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 · dispatcher.parseSkillsOptions (cognitive 16) · ×1
  • dispatcher.parseSkillsOptions (cognitive 16) cli/dispatcher/internal/dispatcher/skills_options.go:18 — dispatcher.parseSkillsOptions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), boolean chains 3, match/switch 1 (2 pts), 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 · verifier.scanDirectory (cognitive 16) · ×1
  • verifier.scanDirectory (cognitive 16) cli/dispatcher/internal/projectverify/meta_scan.go:21 — verifier.scanDirectory has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · projectrunner.probePendingCompileStatus (cognitive 16) · ×1
  • projectrunner.probePendingCompileStatus (cognitive 16) cli/project-runner/internal/projectrunner/compile_attach.go:120 — projectrunner.probePendingCompileStatus has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (2 pts), 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 · projectrunner.runControlPlayModeWithStateWait (cognitive 16) · ×1
  • projectrunner.runControlPlayModeWithStateWait (cognitive 16) cli/project-runner/internal/projectrunner/control_play_mode_wait.go:59 — projectrunner.runControlPlayModeWithStateWait has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · projectrunner.runPausePointWaitAfterEnable (cognitive 16) · ×1
  • projectrunner.runPausePointWaitAfterEnable (cognitive 16) cli/project-runner/internal/projectrunner/pause_point_enable.go:368 — projectrunner.runPausePointWaitAfterEnable has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1 (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 · automation.ParseGoCoverProfile (cognitive 16) · ×1
  • automation.ParseGoCoverProfile (cognitive 16) cli/release-automation/internal/automation/coverage_report.go:160 — automation.ParseGoCoverProfile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · slocScanner.scanCSharpInterpolatedString (cognitive 16) · ×1
  • slocScanner.scanCSharpInterpolatedString (cognitive 16) cli/release-automation/internal/automation/file_length_sloc.go:262 — slocScanner.scanCSharpInterpolatedString has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, 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.
D22 · Internal API Consistency · `skillscan.FindUnityCliLoopPackage` signals absence with comma-ok `(T, bool)` where its 3 sibling single-key reads use a bare `T` (the zero value when absent) · ×1
  • `skillscan.FindUnityCliLoopPackage` signals absence with comma-ok `(T, bool)` where its 3 sibling single-key reads use a bare `T` (the zero value when absent) cli/common/skillscan/packages.go:100 — 3 of 4 single-key reads of `package skillscan` return a bare `T` (the zero value when absent) (3 of 4). Siblings: skillscan.CliOnlySourceRoot (cli/common/skillscan/cli_source.go:7); skillscan.ResolvePackageRoot (cli/common/skillscan/packages.go:223); skillscan.FallbackSkillName (cli/common/skillscan/sources.go:137). Return a bare `T` (the zero value when absent) like its siblings. [rule A5]
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · TooManyFields · ×1
  • TooManyFields: pausePointStatusResponse cli/project-runner/internal/projectrunner/pause_point_types.go:3 — TooManyFields — 60 stored fields. The bar is 30 stored fields; this is 30 over it, 2.00× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: HotReloadConstants Packages/src/Editor/FirstPartyTools/HotReload/Shared/HotReloadConstants.cs — ClassTooLong — 484 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 84 over it, 1.21× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
D3 · God Classes · FunctionTooLong · ×1
  • FunctionTooLong: projectrunner.sendWithTransientConnectionRetryAttempts cli/project-runner/internal/projectrunner/connection_retry.go:255 — FunctionTooLong — sendWithTransientConnectionRetryAttempts runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) cli/dispatcher/internal/dispatcher/skills.go:231 — cli/dispatcher/internal/dispatcher/skills.go:231-266 | cli/dispatcher/internal/dispatcher/skills.go:268-290 | cli/dispatcher/internal/dispatcher/skills_v3_migration.go:13-35 | cli/dispatcher/internal/dispatcher/skills_v3_migration.go:37-59 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (67 corresponding lines) · ×1
  • Edited copy of a member (67 corresponding lines) cli/project-runner/internal/projectrunner/compile_attach.go:267 — cli/project-runner/internal/projectrunner/compile_attach.go:267-334 | cli/project-runner/internal/projectrunner/compile_wait.go:209-275 — These two members are one piece of code written twice and then edited apart: 67 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (88 corresponding lines) · ×1
  • Edited copy of a member (88 corresponding lines) cli/project-runner/internal/projectrunner/pause_point_enable.go:375 — cli/project-runner/internal/projectrunner/pause_point_enable.go:375-471 | cli/project-runner/internal/projectrunner/pause_point_wait.go:311-398 — These two members are one piece of code written twice and then edited apart: 88 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) cli/dispatcher/attestation/verifier.go:79 — cli/dispatcher/attestation/verifier.go:79-121 | cli/dispatcher/attestation/verifier.go:151-186 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) cli/dispatcher/internal/nativepath/path.go:71 — cli/dispatcher/internal/nativepath/path.go:71-99 | cli/dispatcher/internal/nativepath/path.go:103-131 — 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 (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) cli/common/skillscan/sources.go:82 — cli/common/skillscan/sources.go:82-112 | cli/dispatcher/internal/dispatcher/skills_discovery.go:81-121 — 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 (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) cli/dispatcher/internal/dispatcher/skills_dir_status.go:290 — cli/dispatcher/internal/dispatcher/skills_dir_status.go:290-314 | cli/dispatcher/internal/dispatcher/skills_dir_status.go:320-347 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) cli/dispatcher/internal/install/command.go:31 — cli/dispatcher/internal/install/command.go:31-62 | cli/dispatcher/internal/uninstall/command.go:31-58 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 24+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 24+ corresponding lines) cli/release-automation/internal/automation/package_pin_consistency.go:93 — cli/release-automation/internal/automation/package_pin_consistency.go:93-116 | cli/release-automation/internal/automation/package_pin_consistency.go:118-144 | cli/release-automation/internal/automation/package_release_pr_gate.go:62-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 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 (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) cli/project-runner/internal/projectrunner/hot_reload_busy_wait.go:268 — cli/project-runner/internal/projectrunner/hot_reload_busy_wait.go:268-295 | cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go:347-372 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 16+ corresponding lines) cli/release-automation/internal/automation/contract_file_at_ref.go:129 — cli/release-automation/internal/automation/contract_file_at_ref.go:129-149 | cli/release-automation/internal/automation/contract_file_at_ref.go:155-172 | cli/release-automation/internal/automation/git_helpers.go:25-40 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×1
  • Edited copy of a member (24 corresponding lines) cli/dispatcher/internal/dispatcher/launch.go:417 — cli/dispatcher/internal/dispatcher/launch.go:417-440 | cli/dispatcher/internal/dispatcher/launch_v2_lockfile.go:51-75 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) cli/project-runner/internal/projectrunner/pause_point_clear_file_line.go:108 — cli/project-runner/internal/projectrunner/pause_point_clear_file_line.go:108-136 | cli/project-runner/internal/projectrunner/record_video_one_shot_options.go:150-172 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 20+ corresponding lines) cli/common/errors/error_envelope.go:274 — cli/common/errors/error_envelope.go:274-293 | cli/common/errors/error_envelope_classification.go:71-90 | cli/common/errors/error_envelope_classification.go:92-114 | cli/common/errors/error_envelope_classification.go:119-138 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 17+ corresponding lines) cli/project-runner/internal/projectrunner/compile_attach.go:400 — cli/project-runner/internal/projectrunner/compile_attach.go:400-416 | cli/project-runner/internal/projectrunner/compile_attach.go:420-437 | cli/project-runner/internal/projectrunner/compile_attach.go:439-456 | cli/project-runner/internal/projectrunner/compile_fresh_recovery.go:148-166 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) cli/dispatcher/internal/compilecheck/fastcheck/client.go:219 — cli/dispatcher/internal/compilecheck/fastcheck/client.go:219-233 | cli/dispatcher/internal/compilecheck/surface_verdict.go:204-218 | REDACTED:76-88 — 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 (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) cli/dispatcher/internal/dispatcher/compile_check.go:399 — cli/dispatcher/internal/dispatcher/compile_check.go:399-411 | cli/dispatcher/internal/dispatcher/compile_check.go:414-426 | cli/dispatcher/internal/dispatcher/launch_log_file.go:29-44 | cli/dispatcher/internal/dispatcher/launch_options.go:120-131 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) cli/dispatcher/internal/compilecheck/scheduler.go:223 — cli/dispatcher/internal/compilecheck/scheduler.go:223-239 | cli/dispatcher/internal/compilecheck/scheduler.go:252-266 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 14+ corresponding lines) cli/project-runner/internal/projectrunner/connection_retry_focus_log.go:19 — cli/project-runner/internal/projectrunner/connection_retry_focus_log.go:19-33 | cli/project-runner/internal/projectrunner/connection_retry_focus_log.go:42-56 | cli/project-runner/internal/projectrunner/connection_retry_focus_log.go:66-81 | cli/project-runner/internal/projectrunner/connection_retry_focus_log.go:89-102 | cli/project-runner/internal/projectrunner/connection_retry_focus_log.go:111-125 | cli/project-runner/internal/projectrunner/connection_retry_focus_log.go:133-146 | cli/project-runner/internal/projectrunner/connection_retry_focus_log.go:154-167 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) cli/dispatcher/cmd/dispatcher/main.go:12 — cli/dispatcher/cmd/dispatcher/main.go:12-17 | cli/project-runner/cmd/project-runner/main.go:12-17 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) cli/dispatcher/internal/compilecheck/input_key_identity.go:76 — cli/dispatcher/internal/compilecheck/input_key_identity.go:76-85 | cli/dispatcher/internal/compilecheck/predefined_sources.go:98-114 — 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 (8 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 3+ corresponding lines) cli/release-automation/cmd/cancel-superseded-waiting-runs/main.go:10 — cli/release-automation/cmd/cancel-superseded-waiting-runs/main.go:10-12 | cli/release-automation/cmd/check-package-pin-consistency/main.go:14-16 | cli/release-automation/cmd/create-unity-package-release/main.go:14-16 | cli/release-automation/cmd/merge-package-release-pr/main.go:13-15 | cli/release-automation/cmd/plan-unity-package-release/main.go:15-17 | cli/release-automation/cmd/publish-coverage-trend/main.go:10-12 | cli/release-automation/cmd/update-homebrew-formula/main.go:10-12 | cli/release-automation/cmd/update-winget-manifest/main.go:10-12 — These 8 members are one piece of code written 8 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 8 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) cli/common/errors/command_suggestions.go:49 — cli/common/errors/command_suggestions.go:49-73 | cli/project-runner/internal/projectrunner/tool_param_suggestions.go:249-273 — 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 `cli/common/errors/command_suggestions.go:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Check import visibility before settling on that home: `cli/project-runner/internal/projectrunner/tool_param_suggestions.go` sits under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.
D4 · Code Duplication · Duplicated block (19–20 lines × 2) · ×1
  • Duplicated block (19–20 lines × 2) cli/project-runner/internal/projectrunner/pause_point_enable.go:453 — cli/project-runner/internal/projectrunner/pause_point_enable.go:453-471 | cli/project-runner/internal/projectrunner/pause_point_wait.go:379-398 — 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 `cli/project-runner/internal/projectrunner/pause_point_enable.go:453` 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) cli/project-runner/internal/projectrunner/compile_attach.go:279 — cli/project-runner/internal/projectrunner/compile_attach.go:279-297 | cli/project-runner/internal/projectrunner/compile_wait.go:221-239 — 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 `cli/project-runner/internal/projectrunner/compile_attach.go:279` 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.
D4 · Code Duplication · Duplicated block (12–16 lines × 2) · ×1
  • Duplicated block (12–16 lines × 2) cli/project-runner/internal/projectrunner/pause_point_enable.go:395 — cli/project-runner/internal/projectrunner/pause_point_enable.go:395-410 | cli/project-runner/internal/projectrunner/pause_point_wait.go:332-343 — 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 `cli/project-runner/internal/projectrunner/pause_point_enable.go:395` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) cli/dispatcher/internal/dispatcher/skills.go:275 — cli/dispatcher/internal/dispatcher/skills.go:275-286 | cli/dispatcher/internal/dispatcher/skills_v3_migration.go:44-55 — 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. 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 (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) cli/dispatcher/internal/dispatcher/skills.go:258 — cli/dispatcher/internal/dispatcher/skills.go:258-266 | cli/dispatcher/internal/dispatcher/skills.go:282-290 | cli/dispatcher/internal/dispatcher/skills_v3_migration.go:27-35 | cli/dispatcher/internal/dispatcher/skills_v3_migration.go:51-59 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `cli/dispatcher/internal/dispatcher/skills.go:258` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `cli/dispatcher/internal/dispatcher/skills.go:256` calls `WriteFormat` and `cli/dispatcher/internal/dispatcher/skills_v3_migration.go:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) cli/dispatcher/internal/dispatcher/dispatcher_v2_run.go:123 — cli/dispatcher/internal/dispatcher/dispatcher_v2_run.go:123-129 | cli/dispatcher/internal/dispatcher/run_dispatcher.go:296-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 `cli/dispatcher/internal/dispatcher/dispatcher_v2_run.go:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) cli/common/version/compare.go:80 — cli/common/version/compare.go:80-86 | cli/dispatcher/internal/dispatcher/dispatcher_pin.go:98-104 | cli/release-automation/internal/automation/protocol_minimum_version_guard.go:199-205 — 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. Check import visibility before settling on that home: `cli/dispatcher/internal/dispatcher/dispatcher_pin.go`, `cli/release-automation/internal/automation/protocol_minimum_version_guard.go` sit under a restricted `internal` directory, which only code inside its own subtree is permitted to import from — so it is reachable from some of these sites and not from others, and being able to see the copies is not the same as being allowed to share them. The home has to be somewhere every one of these sites is permitted to import from; if there is no such place, that restriction may be exactly why the copies are separate.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs:75 — tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs:75-94 | tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs:113-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) tools/UnityCliLoop.DeadCodeScanner/UnityKeeperClassifier.cs:116 — tools/UnityCliLoop.DeadCodeScanner/UnityKeeperClassifier.cs:116-133 | tools/UnityCliLoop.DeadCodeScanner/UnityKeeperClassifier.cs:255-272 — 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 `tools/UnityCliLoop.DeadCodeScanner/UnityKeeperClassifier.cs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D44 · Platform End-of-Life · End-of-life runtime · ×1
  • End-of-life runtime: .NET net6.0 tests/CompileCheckWorker.UnitTests/CompileCheckWorker.UnitTests.csproj:4 — tests/CompileCheckWorker.UnitTests/CompileCheckWorker.UnitTests.csproj declares .NET net6.0 as this project's target framework, and .NET 6 LTS, support ended 2024-11-12. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2024-11-12 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.Editor — UnityCLILoop.FirstPartyTools.Editor has instability 0.90 with 2 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.HotReload.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.HotReload.Editor — UnityCLILoop.FirstPartyTools.HotReload.Editor has instability 0.89 with 1 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.HotReload.Patching.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.HotReload.Patching.Editor — UnityCLILoop.FirstPartyTools.HotReload.Patching.Editor has instability 0.83 with 1 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.RecordInput.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.RecordInput.Editor — UnityCLILoop.FirstPartyTools.RecordInput.Editor has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.RecordVideo.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.RecordVideo.Editor — UnityCLILoop.FirstPartyTools.RecordVideo.Editor has instability 0.83 with 1 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.ReplayInput.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.ReplayInput.Editor — UnityCLILoop.FirstPartyTools.ReplayInput.Editor has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.Screenshot.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.Screenshot.Editor — UnityCLILoop.FirstPartyTools.Screenshot.Editor has instability 0.82 with 2 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor — UnityCLILoop.FirstPartyTools.SimulateKeyboard.Editor has instability 0.89 with 1 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor — UnityCLILoop.FirstPartyTools.SimulateMouseInput.Editor has instability 0.90 with 1 dependents.
D5 · Coupling · Unstable project UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor · ×1
  • Unstable project UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor — UnityCLILoop.FirstPartyTools.SimulateMouseUi.Editor has instability 0.91 with 1 dependents.
D5 · Coupling · Unstable project UnityCLILoop.Infrastructure · ×1
  • Unstable project UnityCLILoop.Infrastructure — UnityCLILoop.Infrastructure has instability 0.88 with 1 dependents.
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.
S1 · Cryptographic Hygiene · Weak hash algorithm · ×1
  • Weak hash algorithm Packages/src/Editor/FirstPartyTools/HotReload/Shared/HotReloadSourceBaseline.cs:369 — MD5/SHA1 is constructed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ for content integrity, or a KDF (PBKDF2/Argon2/BCrypt) for password storage. If it only derives a non-security identifier (a cache key, a file or mutex name), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as `System.IO.Hashing.XxHash64`/`Crc32` says it in code — since the algorithm alone cannot distinguish the two uses.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×1
  • JavaScript dependencies are not locked Packages/src/package.json:14 — Packages/src/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
Minor — 61 finding(s)
X7 · Silent fallback defaults · Silent fallback default on error · ×31
  • Silent fallback default on error cli/common/clicore/server_not_responding.go:7 — `resolveProjectEndpointAddress` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/clicore/tool_settings.go:27 — `LoadDisabledTools` turns a non-nil `err` into `return []string{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/skillscan/packages.go:126 — `enumerateDirectProjectPackageResults` turns a non-nil `err` into `return []PackageSearchResult{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/skillscan/packages.go:177 — `enumeratePackageCacheResults` turns a non-nil `err` into `return []PackageSearchResult{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/skillscan/packages.go:205 — `enumerateUnityCliLoopPackageCacheFallbackResults` turns a non-nil `err` into `return []PackageSearchResult{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/skillscan/packages.go:232 — `resolvePackageRootCandidate` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/skillscan/packages.go:272 — `readManifestDependencies` turns a non-nil `err` into `return map[string]string{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/skillscan/sources.go:66 — `scanInternalSkillToolNames` turns a non-nil `err` into `return []string{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/tools/catalog.go:49 — `LoadDefault` turns a non-nil `err` into `return ToolCatalog{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/unityprocess/lsappinfo_output.go:23 — `parseLsappinfoPID` turns a non-nil `err` into `return 0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/unityprocess/focus_darwin.go:38 — `readFrontmostProcessIDMac` turns a non-nil `err` into `return 0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/unityprocess/focus_darwin.go:54 — `bundlePathForPIDMac` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/common/unityprocess/focus_darwin.go:72 — `countProcessesWithBundlePathMac` turns a non-nil `err` into `return 0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/compilecheck/source_set.go:152 — `readAssemblyDefinitionGUID` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/compilecheck/result_cache.go:141 — `nonSourceKeyBeforeCompile` turns a non-nil `err` into `return nonSourceIdentity{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/dispatcher/dispatcher_freshness.go:81 — `detectManagedDispatcherInstall` turns a non-nil `err` into `return sharedupdate.ManagedInstall{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/dispatcher/dispatcher_update_version.go:49 — `dispatcherInstalledVersionOrEmpty` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/dispatcher/dispatcher_v2_detect.go:173 — `detectV2DispatcherFileDependencyProject` turns a non-nil `err` into `return dispatcherV2Project{}, nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/dispatcher/dispatcher_v2_detect.go:250 — `detectV2DispatcherPackageAtPath` turns a non-nil `err` into `return dispatcherV2Project{}, nil` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/dispatcher/dispatcher_version_hold.go:47 — `readDispatcherVersionHold` turns a non-nil `err` into `return false, ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/dispatcher/dispatcher_version_hold.go:70 — `snapshotDispatcherVersionHold` turns a non-nil `err` into `return dispatcherVersionHoldSnapshot{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/dispatcher/dispatcher_version_human.go:54 — `dispatcherVersionContextSentence` turns a non-nil `err` into `return "No Unity project detected here; run inside a Unity project to see which CLI generation serves it."` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/dispatcher/launch.go:485 — `unityExecutableCandidates` turns a non-nil `err` into `return []string{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/githubapi/ratelimit.go:146 — `parseResetHeader` turns a non-nil `err` into `return time.Time{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • Silent fallback default on error cli/dispatcher/internal/githubapi/ratelimit.go:154 — `parseRetryAfterHeader` turns a non-nil `err` into `return time.Time{}` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the `if` or in the doc comment, and the row stops firing.
  • + 6 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×15
  • Duplicated predicate tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs:132 — `argument == "--help" || argument == "-h"` appears character-identically in 3 files — tools/UnityCliLoop.CodeComplexity/CommandLineOptions.cs, tools/UnityCliLoop.DeadCodeScanner/CommandLineOptions.cs, tools/UnityCliLoop.DeadCodeScanner/Program.cs. 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 cli/dispatcher/internal/dispatcher/compile_check.go:382 — `arg == option || strings.HasPrefix(arg, option+"=")` appears character-identically in 3 files — cli/dispatcher/internal/dispatcher/compile_check.go, cli/dispatcher/internal/dispatcher/launch_options.go, cli/project-runner/internal/projectrunner/pause_point_clear_file_line.go. 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 cli/dispatcher/internal/dispatcher/launch_newer_protocol.go:53 — `ctx.Err() == nil && isNewerDispatcherProtocolMismatch(err)` appears character-identically in 2 files — cli/dispatcher/internal/dispatcher/launch_newer_protocol.go, cli/dispatcher/internal/dispatcher/launch_startup_timeout_error.go. 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 cli/project-runner/internal/projectrunner/hot_reload_busy_wait.go:88 — `err == nil && hasHotReloadTiming(merged)` appears character-identically in 2 files — cli/project-runner/internal/projectrunner/hot_reload_busy_wait.go, cli/project-runner/internal/projectrunner/hot_reload_editor_ready_retry.go. 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 cli/common/errors/transport_errors.go:85 — `errors.Is(err, os.ErrDeadlineExceeded) || os.IsTimeout(err)` appears character-identically in 2 files — cli/common/errors/transport_errors.go, cli/common/unityipc/client.go. 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 cli/dispatcher/internal/dispatcher/install.go:97 — `index+1 >= len(args) || clicore.IsNextOptionToken(args[index+1])` appears character-identically in 2 files — cli/dispatcher/internal/dispatcher/install.go, cli/project-runner/internal/projectrunner/tool_params.go. 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 cli/dispatcher/internal/dispatcher/dispatcher_process.go:16 — `len(args) == 0 || clicore.IsHelpRequest(args)` appears character-identically in 3 files — cli/dispatcher/internal/dispatcher/dispatcher_process.go, cli/dispatcher/internal/dispatcher/run_dispatcher.go, cli/project-runner/internal/projectrunner/runner_usage.go. 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 cli/dispatcher/internal/dispatcher/package.go:35 — `len(args) == 1 || clicore.IsHelpRequest(args[1:])` appears character-identically in 2 files — cli/dispatcher/internal/dispatcher/package.go, cli/dispatcher/internal/dispatcher/skills.go. 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 cli/dispatcher/internal/dispatcher/dispatcher_v2_run.go:23 — `len(args) > 0 && args[0] == clicore.LaunchCommandName` appears character-identically in 2 files — cli/dispatcher/internal/dispatcher/dispatcher_v2_run.go, cli/dispatcher/internal/dispatcher/run_dispatcher.go. 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 cli/project-runner/internal/projectrunner/pause_point_enable.go:268 — `nestedProjectPath != "" && nestedProjectPath != connection.ProjectRoot` appears character-identically in 2 files — cli/project-runner/internal/projectrunner/pause_point_enable.go, cli/project-runner/internal/projectrunner/runner_commands.go. 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 cli/project-runner/internal/projectrunner/pause_point_trigger_diagnosis.go:128 — `ok && response.Success != nil && !*response.Success` appears character-identically in 2 files — cli/project-runner/internal/projectrunner/pause_point_trigger_diagnosis.go, cli/project-runner/internal/projectrunner/record_video_one_shot.go. 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 cli/dispatcher/internal/dispatcher/attestation_release.go:115 — `response.StatusCode < 200 || response.StatusCode >= 300` appears character-identically in 3 files — cli/dispatcher/internal/dispatcher/attestation_release.go, cli/dispatcher/internal/dispatcher/dispatcher_download.go, cli/dispatcher/internal/dispatcher/package_registry.go. 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 cli/release-automation/internal/automation/dispatcher_pin_freshness.go:224 — `response.StatusCode < http.StatusOK || response.StatusCode >= http.StatusMultipleChoices` appears character-identically in 2 files — cli/release-automation/internal/automation/dispatcher_pin_freshness.go, cli/release-automation/internal/automation/dispatcher_pin_stamp.go. 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 cli/project-runner/internal/projectrunner/pause_point_enable.go:432 — `state == pausePointWaitStateTimeout && !hasNewHitBaseline` appears character-identically in 2 files — cli/project-runner/internal/projectrunner/pause_point_enable.go, cli/project-runner/internal/projectrunner/pause_point_wait.go. 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 cli/common/version/compare.go:82 — `strings.HasPrefix(trimmed, "v") || strings.HasPrefix(trimmed, "V")` appears character-identically in 2 files — cli/common/version/compare.go, cli/dispatcher/internal/dispatcher/dispatcher_pin.go. 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.
D29 · Static Analysis (SAST) · REDACTED · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D20 · ADR Quality · ADR has no Context section · ×1
  • ADR has no Context section docs/adr/0001-csharp-security-scan-engine.md:1 — docs/adr/0001-csharp-security-scan-engine.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D20 · ADR Quality · ADR has no Consequences section · ×1
  • ADR has no Consequences section docs/adr/0002-dispatcher-runner-split.md:1 — docs/adr/0002-dispatcher-runner-split.md has no Consequences section (a heading such as `## Consequences`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P12 · CI test-gate honesty · Sleep-based test synchronization · ×1
  • Sleep-based test synchronization — 26 Task.Delay/Thread.Sleep call(s) in test code synchronize with background work by sleeping — a known flakiness precursor on slow runners. Prefer polling with a deadline or completion signals.
P3 · Security & performance tooling · Dependabot does not watch nuget/npm · ×1
  • Dependabot does not watch nuget/npm REDACTED:3 — `REDACTED` schedules updates, but no `package-ecosystem` entry covers `nuget`, `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list.
X9 · Subsumed condition operand · Subsumed condition operand · ×1
  • Subsumed condition operand cli/project-runner/internal/projectrunner/pause_point_status_expect_test.go:169 — `strings.Contains(output, "AllExpectationsPassed")` can never decide this `||` — every value satisfying `strings.Contains(output, "AllExpectationsPassed")` also satisfies `strings.Contains(output, "Expectations")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Minor — 12 finding(s)
D5 · Coupling · Off the main sequence · ×11
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.GameView.Editor — UnityCLILoop.FirstPartyTools.Common.GameView.Editor: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.MouseUi.Editor — UnityCLILoop.FirstPartyTools.Common.MouseUi.Editor: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.OutputRetention.Editor — UnityCLILoop.FirstPartyTools.Common.OutputRetention.Editor: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.ScriptPath.Editor — UnityCLILoop.FirstPartyTools.Common.ScriptPath.Editor: abstractness 0.00, instability 0.00, distance 1.00 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: github.com/hatayama/unity-cli-loop/common — github.com/hatayama/unity-cli-loop/common: abstractness 0.02, instability 0.00, distance 0.98 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.Overlay.Editor — UnityCLILoop.FirstPartyTools.Common.Overlay.Editor: abstractness 0.00, instability 0.11, distance 0.89 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.Console.Editor — UnityCLILoop.FirstPartyTools.Common.Console.Editor: abstractness 0.13, instability 0.00, distance 0.88 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.ToolContracts — UnityCLILoop.ToolContracts: abstractness 0.17, instability 0.00, distance 0.83 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.InputSimulation.Editor — UnityCLILoop.FirstPartyTools.Common.InputSimulation.Editor: abstractness 0.00, instability 0.20, distance 0.80 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.Preflight.Editor — UnityCLILoop.FirstPartyTools.Common.Preflight.Editor: abstractness 0.00, instability 0.25, distance 0.75 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: UnityCLILoop.FirstPartyTools.Common.EditorUtility.Editor — UnityCLILoop.FirstPartyTools.Common.EditorUtility.Editor: abstractness 0.27, instability 0.00, distance 0.73 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
D12 · Dependency Hygiene · Outdated · ×1
  • Outdated: golang.org/x/term — `golang.org/x/term` is required at v0.47.0 in REDACTED, but v0.48.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get golang.org/x/term@v0.48.0 && go mod tidy` and commit the updated REDACTED and go.sum.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-fdb0d624e7594a7099c44be3539d5d94/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-fdb0d624e7594a7099c44be3539d5d94/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=1458" --report-format json --report-path /tmp/watchdog-gitleaks-fdb0d624e7594a7099c44be3539d5d94/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.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-fdb0d624e7594a7099c44be3539d5d94/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 .18artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .8artifacts/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.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 01a1e8a3-8f29-7a92-9f69-96ce988a2559 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Appendix C — Personal-data map

Every field, property and record parameter whose name is conventional personal data — 1 field(s) across 1 category, each with an exact repo-relative file:line. This is the data inventory a compliance review starts from — right-to-erasure, retention, minimisation. Detected by NAME, from the C# syntax tree, with a deliberately specific identifier classifier — the same one the C1–C5 compliance cards use to decide whether personal data is present, so CardDefinition or FileName don't trip. Two caveats stated rather than glossed: those cards additionally require corroboration (a persistence/account signal, or two distinct PII categories) that this inventory deliberately does not, so it lists more than they gate on; and D32 Data Compliance shares nothing with it — that dimension is a separate semgrep ruleset for personal data leaking into logs, URLs and browser storage, and a clean D32 result says nothing about this list. Informational — it feeds no score.

Name — 1 field(s)
  • DeadCodeIssue.FullName tools/UnityCliLoop.DeadCodeScanner/DeadCodeModels.cs:106

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