Public report of exo-explore/exo, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 01:03 UTC · Survey ID cd_fe78095ffb954720b316b69577db73f3
exo-explore/exo
Measured 14 November 2026, 01:03 UTC, at code version a60b956
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).
CAI scoreAt riskUp 3 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 73,240 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Code Health, 29
Findings by how serious they are
84 critical695 serious93 minor
16 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 01:03 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
76of 76 dimensions measured by tools.
842of 872 findings point to an exact file and line, so you can open each one in the code. The other 30 concern the repository as a whole, such as missing documentation.
76dimensions across 8 lenses, read from 73,240 lines of product code in 6 projects.
exo-explore/exo is rated At risk because critical security findings are open. It scores 41 out of 100, which the At risk rating leaves unchanged.
Code Health, at 29, is the weakest lens and counts most in the score. The best first steps are splitting the oversized files and removing the unused code, each worth about 4 points. Raising Code Health to 70 would lift the score to about 50.
Twenty-four known security holes in the packages the code depends on can be used by attackers. Fourteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and nineteen form fields can't be read by a screen reader. Updating the vulnerable packages, pinning each tool to an exact version and labelling the form fields would close these risks. The three passwords or keys in the code's history need replacing, with the old ones switched off. The three places where the code runs text as code or as a command need a direct call instead. The six controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 73,240 lines, about €100,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 forThe 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.
If Code Health rose from 29 to 70, the lowest score rated Strong, the score would rise from 41 to about 50.
Code composition: what the lines of code are
Product code 61%Tests 39%
New since the last survey: 311 findings
These 311 critical or serious findings weren't in the previous survey, on 25 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
God Classes · FileTooLong: deepseek_v4/model.py src/exo/worker/engines/mlx/models/deepseek_v4/model.py
God Classes · FileTooLong: deepseek_v41/model.py src/exo/worker/engines/mlx/models/deepseek_v41/model.py
God Classes · FileTooLong: testkit/cluster.py src/exo/testkit/cluster.py
God Classes · TooManyMethods: Cluster src/exo/testkit/cluster.py
God Classes · FileTooLong: qwen3/qwen4_exp.py src/exo/worker/engines/mlx/models/qwen3/qwen4_exp.py
God Classes · FileTooLong: deepseek_v41/encoding.py src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py
God Classes · FileTooLong: glm/glm5_next.py src/exo/worker/engines/mlx/models/glm/glm5_next.py
God Classes · FileTooLong: runner/supervisor.py src/exo/worker/runner/supervisor.py
God Classes · FileTooLong: inkling/model.py src/exo/worker/engines/mlx/models/inkling/model.py
God Classes · FileTooLong: shared/apply.py src/exo/shared/apply.py
God Classes · FileTooLong: exo/main.py src/exo/main.py
God Classes · FileTooLong: llm_inference/batch_generator.py src/exo/worker/runner/llm_inference/batch_generator.py
Code Duplication · Near-duplicate member pair (127 shared lines) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py
Code Duplication · Edited copy of a member (31 corresponding lines) src/exo/worker/runner/llm_inference/batch_generator.py
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) src/exo/worker/engines/mlx/models/glm/sharding.py
Code Duplication · Edited copy of a member (149 corresponding lines) src/exo/worker/engines/image/pipeline/runner.py
Code Duplication · Edited copy of a member (55 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py
Code Duplication · Edited copy of a member (69 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 158 findings
These 158 critical or serious findings were in the previous survey, on 25 October 2026, and are gone from this one. The first 100 are listed here.
€34,000 to €170,000, for 569 to 1,807 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 41. 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.
Size
Medium: 73,240 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Raises the score by about 4 points · Medium effort · Large Files
2
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
Raises the score by about 4 points · Medium effort · Dead Code
3
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
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 €100,000 to build again, about 0.7 person-years of work. Its weakest lens is Code Health, at 29 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 109,806 lines over the last 90 days, which is about 445,324 lines a year. At that pace, the extra work comes to an estimated 25.7 to 154.5 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
227 modules, with 387 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; 187 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.
src.exo.shared.types.common uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.common, while a change to src.exo.shared.types.common can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.common uses a module listed above it, which is the healthy direction.
src.exo.shared.types.memory uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.memory, while a change to src.exo.shared.types.memory can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.memory uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.image.models.base uses src.exo.worker.engines.image.config, so a change to src.exo.worker.engines.image.config can break src.exo.worker.engines.image.models.base, while a change to src.exo.worker.engines.image.models.base can't break src.exo.worker.engines.image.config.
Position
Below the diagonal: src.exo.worker.engines.image.models.base uses a module listed above it, which is the healthy direction.
src.exo.routing.membership uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.routing.membership, while a change to src.exo.routing.membership can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.routing.membership uses a module listed above it, which is the healthy direction.
src.exo.routing.membership uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.routing.membership, while a change to src.exo.routing.membership can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.routing.membership uses a module listed above it, which is the healthy direction.
src.exo.shared.models.model_cards uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.models.model_cards, while a change to src.exo.shared.models.model_cards can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.models.model_cards uses a module listed above it, which is the healthy direction.
src.exo.shared.models.model_cards uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.models.model_cards, while a change to src.exo.shared.models.model_cards can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.models.model_cards uses a module listed above it, which is the healthy direction.
src.exo.shared.models.model_cards uses src.exo.shared.types.memory, so a change to src.exo.shared.types.memory can break src.exo.shared.models.model_cards, while a change to src.exo.shared.models.model_cards can't break src.exo.shared.types.memory.
Position
Below the diagonal: src.exo.shared.models.model_cards uses a module listed above it, which is the healthy direction.
src.exo.shared.types.text_generation uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.types.text_generation, while a change to src.exo.shared.types.text_generation can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.types.text_generation uses a module listed above it, which is the healthy direction.
src.exo.shared.types.topology uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.topology, while a change to src.exo.shared.types.topology can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.topology uses a module listed above it, which is the healthy direction.
src.exo.shared.types.topology uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.types.topology, while a change to src.exo.shared.types.topology can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.types.topology uses a module listed above it, which is the healthy direction.
src.exo.shared.types.worker.runners uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.worker.runners, while a change to src.exo.shared.types.worker.runners can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.worker.runners uses a module listed above it, which is the healthy direction.
src.exo.shared.types.worker.runners uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.types.worker.runners, while a change to src.exo.shared.types.worker.runners can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.types.worker.runners uses a module listed above it, which is the healthy direction.
src.exo.api.serving_client uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.api.serving_client, while a change to src.exo.api.serving_client can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.api.serving_client uses a module listed above it, which is the healthy direction.
src.exo.api.serving_client uses src.exo.routing.membership, so a change to src.exo.routing.membership can break src.exo.api.serving_client, while a change to src.exo.api.serving_client can't break src.exo.routing.membership.
Position
Below the diagonal: src.exo.api.serving_client uses a module listed above it, which is the healthy direction.
src.exo.download uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.download, while a change to src.exo.download can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.download uses a module listed above it, which is the healthy direction.
src.exo.download uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.download, while a change to src.exo.download can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.download uses a module listed above it, which is the healthy direction.
src.exo.download.coordinator uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.download.coordinator, while a change to src.exo.download.coordinator can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.download.coordinator uses a module listed above it, which is the healthy direction.
src.exo.download.coordinator uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.download.coordinator, while a change to src.exo.download.coordinator can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.download.coordinator uses a module listed above it, which is the healthy direction.
src.exo.main uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.main, while a change to src.exo.main can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.main uses a module listed above it, which is the healthy direction.
src.exo.main uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.main, while a change to src.exo.main can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.main uses a module listed above it, which is the healthy direction.
src.exo.main uses src.exo.routing.membership, so a change to src.exo.routing.membership can break src.exo.main, while a change to src.exo.main can't break src.exo.routing.membership.
Position
Below the diagonal: src.exo.main uses a module listed above it, which is the healthy direction.
src.exo.shared.topology uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.topology, while a change to src.exo.shared.topology can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.topology uses a module listed above it, which is the healthy direction.
src.exo.shared.topology uses src.exo.shared.types.topology, so a change to src.exo.shared.types.topology can break src.exo.shared.topology, while a change to src.exo.shared.topology can't break src.exo.shared.types.topology.
Position
Below the diagonal: src.exo.shared.topology uses a module listed above it, which is the healthy direction.
src.exo.shared.types.worker.instances uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.worker.instances, while a change to src.exo.shared.types.worker.instances can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.worker.instances uses a module listed above it, which is the healthy direction.
src.exo.shared.types.worker.instances uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.types.worker.instances, while a change to src.exo.shared.types.worker.instances can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.types.worker.instances uses a module listed above it, which is the healthy direction.
src.exo.shared.types.worker.instances uses src.exo.shared.types.worker.runners, so a change to src.exo.shared.types.worker.runners can break src.exo.shared.types.worker.instances, while a change to src.exo.shared.types.worker.instances can't break src.exo.shared.types.worker.runners.
Position
Below the diagonal: src.exo.shared.types.worker.instances uses a module listed above it, which is the healthy direction.
src.exo.shared.types.worker.shards uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.worker.shards, while a change to src.exo.shared.types.worker.shards can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.worker.shards uses a module listed above it, which is the healthy direction.
src.exo.shared.types.worker.shards uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.shared.types.worker.shards, while a change to src.exo.shared.types.worker.shards can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.shared.types.worker.shards uses a module listed above it, which is the healthy direction.
src.exo.api.types.api uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.api.types.api, while a change to src.exo.api.types.api can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.api.types.api uses a module listed above it, which is the healthy direction.
src.exo.api.types.api uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.api.types.api, while a change to src.exo.api.types.api can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.api.types.api uses a module listed above it, which is the healthy direction.
src.exo.api.types.api uses src.exo.shared.types.memory, so a change to src.exo.shared.types.memory can break src.exo.api.types.api, while a change to src.exo.api.types.api can't break src.exo.shared.types.memory.
Position
Below the diagonal: src.exo.api.types.api uses a module listed above it, which is the healthy direction.
src.exo.api.types.api uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.api.types.api, while a change to src.exo.api.types.api can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.api.types.api uses a module listed above it, which is the healthy direction.
src.exo.api.types.api uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.api.types.api, while a change to src.exo.api.types.api can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.api.types.api uses a module listed above it, which is the healthy direction.
src.exo.api.types.api uses src.exo.shared.types.worker.shards, so a change to src.exo.shared.types.worker.shards can break src.exo.api.types.api, while a change to src.exo.api.types.api can't break src.exo.shared.types.worker.shards.
Position
Below the diagonal: src.exo.api.types.api uses a module listed above it, which is the healthy direction.
src.exo.shared.types.deployments uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.deployments, while a change to src.exo.shared.types.deployments can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.deployments uses a module listed above it, which is the healthy direction.
src.exo.shared.types.deployments uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.types.deployments, while a change to src.exo.shared.types.deployments can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.types.deployments uses a module listed above it, which is the healthy direction.
src.exo.shared.types.deployments uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.shared.types.deployments, while a change to src.exo.shared.types.deployments can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.shared.types.deployments uses a module listed above it, which is the healthy direction.
src.exo.shared.types.deployments uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.shared.types.deployments, while a change to src.exo.shared.types.deployments can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.shared.types.deployments uses a module listed above it, which is the healthy direction.
src.exo.shared.types.deployments uses src.exo.shared.types.worker.shards, so a change to src.exo.shared.types.worker.shards can break src.exo.shared.types.deployments, while a change to src.exo.shared.types.deployments can't break src.exo.shared.types.worker.shards.
Position
Below the diagonal: src.exo.shared.types.deployments uses a module listed above it, which is the healthy direction.
src.exo.shared.types.state uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.state, while a change to src.exo.shared.types.state can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.state uses a module listed above it, which is the healthy direction.
src.exo.shared.types.state uses src.exo.shared.topology, so a change to src.exo.shared.topology can break src.exo.shared.types.state, while a change to src.exo.shared.types.state can't break src.exo.shared.topology.
Position
Below the diagonal: src.exo.shared.types.state uses a module listed above it, which is the healthy direction.
src.exo.testkit.cluster uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.testkit.cluster, while a change to src.exo.testkit.cluster can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.testkit.cluster uses a module listed above it, which is the healthy direction.
src.exo.testkit.cluster uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.testkit.cluster, while a change to src.exo.testkit.cluster can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.testkit.cluster uses a module listed above it, which is the healthy direction.
src.exo.testkit.cluster uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.testkit.cluster, while a change to src.exo.testkit.cluster can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.testkit.cluster uses a module listed above it, which is the healthy direction.
src.exo.testkit.cluster uses src.exo.shared.types.worker.shards, so a change to src.exo.shared.types.worker.shards can break src.exo.testkit.cluster, while a change to src.exo.testkit.cluster can't break src.exo.shared.types.worker.shards.
Position
Below the diagonal: src.exo.testkit.cluster uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.mlx uses src.exo.worker.engines.mlx.types, so a change to src.exo.worker.engines.mlx.types can break src.exo.worker.engines.mlx, while a change to src.exo.worker.engines.mlx can't break src.exo.worker.engines.mlx.types.
Position
Below the diagonal: src.exo.worker.engines.mlx uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.mlx uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.worker.engines.mlx, while a change to src.exo.worker.engines.mlx can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.worker.engines.mlx uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.mlx uses src.exo.shared.types.memory, so a change to src.exo.shared.types.memory can break src.exo.worker.engines.mlx, while a change to src.exo.worker.engines.mlx can't break src.exo.shared.types.memory.
Position
Below the diagonal: src.exo.worker.engines.mlx uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.mlx uses src.exo.shared.types.text_generation, so a change to src.exo.shared.types.text_generation can break src.exo.worker.engines.mlx, while a change to src.exo.worker.engines.mlx can't break src.exo.shared.types.text_generation.
Position
Below the diagonal: src.exo.worker.engines.mlx uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.mlx uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.worker.engines.mlx, while a change to src.exo.worker.engines.mlx can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.worker.engines.mlx uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.mlx uses src.exo.shared.types.worker.shards, so a change to src.exo.shared.types.worker.shards can break src.exo.worker.engines.mlx, while a change to src.exo.worker.engines.mlx can't break src.exo.shared.types.worker.shards.
Position
Below the diagonal: src.exo.worker.engines.mlx uses a module listed above it, which is the healthy direction.
src.exo.api.adapters uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.api.adapters, while a change to src.exo.api.adapters can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.api.adapters uses a module listed above it, which is the healthy direction.
src.exo.api.adapters uses src.exo.shared.types.text_generation, so a change to src.exo.shared.types.text_generation can break src.exo.api.adapters, while a change to src.exo.api.adapters can't break src.exo.shared.types.text_generation.
Position
Below the diagonal: src.exo.api.adapters uses a module listed above it, which is the healthy direction.
src.exo.api.adapters uses src.exo.api.types.api, so a change to src.exo.api.types.api can break src.exo.api.adapters, while a change to src.exo.api.adapters can't break src.exo.api.types.api.
Position
Below the diagonal: src.exo.api.adapters uses a module listed above it, which is the healthy direction.
src.exo.shared.types.commands uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.commands, while a change to src.exo.shared.types.commands can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.commands uses a module listed above it, which is the healthy direction.
src.exo.shared.types.commands uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.types.commands, while a change to src.exo.shared.types.commands can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.types.commands uses a module listed above it, which is the healthy direction.
src.exo.shared.types.commands uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.shared.types.commands, while a change to src.exo.shared.types.commands can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.shared.types.commands uses a module listed above it, which is the healthy direction.
src.exo.shared.types.commands uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.shared.types.commands, while a change to src.exo.shared.types.commands can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.shared.types.commands uses a module listed above it, which is the healthy direction.
src.exo.shared.types.commands uses src.exo.shared.types.deployments, so a change to src.exo.shared.types.deployments can break src.exo.shared.types.commands, while a change to src.exo.shared.types.commands can't break src.exo.shared.types.deployments.
Position
Below the diagonal: src.exo.shared.types.commands uses a module listed above it, which is the healthy direction.
src.exo.shared.types.tasks uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.tasks, while a change to src.exo.shared.types.tasks can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.tasks uses a module listed above it, which is the healthy direction.
src.exo.shared.types.tasks uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.types.tasks, while a change to src.exo.shared.types.tasks can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.types.tasks uses a module listed above it, which is the healthy direction.
src.exo.shared.types.tasks uses src.exo.shared.types.text_generation, so a change to src.exo.shared.types.text_generation can break src.exo.shared.types.tasks, while a change to src.exo.shared.types.tasks can't break src.exo.shared.types.text_generation.
Position
Below the diagonal: src.exo.shared.types.tasks uses a module listed above it, which is the healthy direction.
src.exo.shared.types.tasks uses src.exo.shared.types.worker.runners, so a change to src.exo.shared.types.worker.runners can break src.exo.shared.types.tasks, while a change to src.exo.shared.types.tasks can't break src.exo.shared.types.worker.runners.
Position
Below the diagonal: src.exo.shared.types.tasks uses a module listed above it, which is the healthy direction.
src.exo.shared.types.tasks uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.shared.types.tasks, while a change to src.exo.shared.types.tasks can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.shared.types.tasks uses a module listed above it, which is the healthy direction.
src.exo.shared.types.tasks uses src.exo.api.types.api, so a change to src.exo.api.types.api can break src.exo.shared.types.tasks, while a change to src.exo.shared.types.tasks can't break src.exo.api.types.api.
Position
Below the diagonal: src.exo.shared.types.tasks uses a module listed above it, which is the healthy direction.
src.exo.testkit uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.testkit, while a change to src.exo.testkit can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.testkit uses a module listed above it, which is the healthy direction.
src.exo.testkit uses src.exo.shared.topology, so a change to src.exo.shared.topology can break src.exo.testkit, while a change to src.exo.testkit can't break src.exo.shared.topology.
Position
Below the diagonal: src.exo.testkit uses a module listed above it, which is the healthy direction.
src.exo.testkit uses src.exo.testkit.cluster, so a change to src.exo.testkit.cluster can break src.exo.testkit, while a change to src.exo.testkit can't break src.exo.testkit.cluster.
Position
Below the diagonal: src.exo.testkit uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.utils.pydantic_ext, so a change to src.exo.utils.pydantic_ext can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.utils.pydantic_ext.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.shared.types.topology, so a change to src.exo.shared.types.topology can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.shared.types.topology.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.shared.types.worker.runners, so a change to src.exo.shared.types.worker.runners can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.shared.types.worker.runners.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.shared.types.deployments, so a change to src.exo.shared.types.deployments can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.shared.types.deployments.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.shared.types.state, so a change to src.exo.shared.types.state can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.shared.types.state.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.shared.types.events uses src.exo.shared.types.tasks, so a change to src.exo.shared.types.tasks can break src.exo.shared.types.events, while a change to src.exo.shared.types.events can't break src.exo.shared.types.tasks.
Position
Below the diagonal: src.exo.shared.types.events uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.base uses src.exo.worker.disaggregated.server, so a change to src.exo.worker.disaggregated.server can break src.exo.worker.engines.base, while a change to src.exo.worker.engines.base can't break src.exo.worker.disaggregated.server.
Position
Below the diagonal: src.exo.worker.engines.base uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.base uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.worker.engines.base, while a change to src.exo.worker.engines.base can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.worker.engines.base uses a module listed above it, which is the healthy direction.
src.exo.worker.engines.base uses src.exo.shared.types.tasks, so a change to src.exo.shared.types.tasks can break src.exo.worker.engines.base, while a change to src.exo.worker.engines.base can't break src.exo.shared.types.tasks.
Position
Below the diagonal: src.exo.worker.engines.base uses a module listed above it, which is the healthy direction.
src.exo.worker.runner.supervisor uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.worker.runner.supervisor, while a change to src.exo.worker.runner.supervisor can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.worker.runner.supervisor uses a module listed above it, which is the healthy direction.
src.exo.worker.runner.supervisor uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.worker.runner.supervisor, while a change to src.exo.worker.runner.supervisor can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.worker.runner.supervisor uses a module listed above it, which is the healthy direction.
src.exo.worker.runner.supervisor uses src.exo.shared.types.tasks, so a change to src.exo.shared.types.tasks can break src.exo.worker.runner.supervisor, while a change to src.exo.worker.runner.supervisor can't break src.exo.shared.types.tasks.
Position
Below the diagonal: src.exo.worker.runner.supervisor uses a module listed above it, which is the healthy direction.
src.exo.api.main uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.api.main, while a change to src.exo.api.main can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.api.main uses a module listed above it, which is the healthy direction.
src.exo.api.main uses src.exo.routing.membership, so a change to src.exo.routing.membership can break src.exo.api.main, while a change to src.exo.api.main can't break src.exo.routing.membership.
Position
Below the diagonal: src.exo.api.main uses a module listed above it, which is the healthy direction.
src.exo.api.main uses src.exo.shared.types.text_generation, so a change to src.exo.shared.types.text_generation can break src.exo.api.main, while a change to src.exo.api.main can't break src.exo.shared.types.text_generation.
Position
Below the diagonal: src.exo.api.main uses a module listed above it, which is the healthy direction.
src.exo.api.main uses src.exo.api.serving_client, so a change to src.exo.api.serving_client can break src.exo.api.main, while a change to src.exo.api.main can't break src.exo.api.serving_client.
Position
Below the diagonal: src.exo.api.main uses a module listed above it, which is the healthy direction.
src.exo.api.main uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.api.main, while a change to src.exo.api.main can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.api.main uses a module listed above it, which is the healthy direction.
src.exo.api.main uses src.exo.shared.types.worker.shards, so a change to src.exo.shared.types.worker.shards can break src.exo.api.main, while a change to src.exo.api.main can't break src.exo.shared.types.worker.shards.
Position
Below the diagonal: src.exo.api.main uses a module listed above it, which is the healthy direction.
31 pairs of types, where a type in src.exo.api.main uses a type in src.exo.api.types.api. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
src.exo.api.main uses src.exo.api.types.api, so a change to src.exo.api.types.api can break src.exo.api.main, while a change to src.exo.api.main can't break src.exo.api.types.api.
Position
Below the diagonal: src.exo.api.main uses a module listed above it, which is the healthy direction.
src.exo.api.main uses src.exo.shared.types.events, so a change to src.exo.shared.types.events can break src.exo.api.main, while a change to src.exo.api.main can't break src.exo.shared.types.events.
Position
Below the diagonal: src.exo.api.main uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.memory, so a change to src.exo.shared.types.memory can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.memory.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.routing.membership, so a change to src.exo.routing.membership can break src.exo.master, while a change to src.exo.master can't break src.exo.routing.membership.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.models.model_cards, so a change to src.exo.shared.models.model_cards can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.models.model_cards.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.topology, so a change to src.exo.shared.types.topology can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.topology.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.worker.runners, so a change to src.exo.shared.types.worker.runners can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.worker.runners.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.topology, so a change to src.exo.shared.topology can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.topology.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.worker.shards, so a change to src.exo.shared.types.worker.shards can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.worker.shards.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.deployments, so a change to src.exo.shared.types.deployments can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.deployments.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.state, so a change to src.exo.shared.types.state can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.state.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.commands, so a change to src.exo.shared.types.commands can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.commands.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.master uses src.exo.shared.types.events, so a change to src.exo.shared.types.events can break src.exo.master, while a change to src.exo.master can't break src.exo.shared.types.events.
Position
Below the diagonal: src.exo.master uses a module listed above it, which is the healthy direction.
src.exo.shared uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.shared, while a change to src.exo.shared can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.shared uses a module listed above it, which is the healthy direction.
src.exo.shared uses src.exo.routing.membership, so a change to src.exo.routing.membership can break src.exo.shared, while a change to src.exo.shared can't break src.exo.routing.membership.
Position
Below the diagonal: src.exo.shared uses a module listed above it, which is the healthy direction.
src.exo.shared uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.shared, while a change to src.exo.shared can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.shared uses a module listed above it, which is the healthy direction.
src.exo.shared uses src.exo.shared.types.deployments, so a change to src.exo.shared.types.deployments can break src.exo.shared, while a change to src.exo.shared can't break src.exo.shared.types.deployments.
Position
Below the diagonal: src.exo.shared uses a module listed above it, which is the healthy direction.
src.exo.shared uses src.exo.shared.types.state, so a change to src.exo.shared.types.state can break src.exo.shared, while a change to src.exo.shared can't break src.exo.shared.types.state.
Position
Below the diagonal: src.exo.shared uses a module listed above it, which is the healthy direction.
src.exo.shared uses src.exo.shared.types.events, so a change to src.exo.shared.types.events can break src.exo.shared, while a change to src.exo.shared can't break src.exo.shared.types.events.
Position
Below the diagonal: src.exo.shared uses a module listed above it, which is the healthy direction.
src.exo.testkit.stub.engine uses src.exo.worker.disaggregated.server, so a change to src.exo.worker.disaggregated.server can break src.exo.testkit.stub.engine, while a change to src.exo.testkit.stub.engine can't break src.exo.worker.disaggregated.server.
Position
Below the diagonal: src.exo.testkit.stub.engine uses a module listed above it, which is the healthy direction.
src.exo.testkit.stub.engine uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.testkit.stub.engine, while a change to src.exo.testkit.stub.engine can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.testkit.stub.engine uses a module listed above it, which is the healthy direction.
src.exo.testkit.stub.engine uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.testkit.stub.engine, while a change to src.exo.testkit.stub.engine can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.testkit.stub.engine uses a module listed above it, which is the healthy direction.
src.exo.testkit.stub.engine uses src.exo.shared.types.tasks, so a change to src.exo.shared.types.tasks can break src.exo.testkit.stub.engine, while a change to src.exo.testkit.stub.engine can't break src.exo.shared.types.tasks.
Position
Below the diagonal: src.exo.testkit.stub.engine uses a module listed above it, which is the healthy direction.
src.exo.testkit.stub.engine uses src.exo.worker.engines.base, so a change to src.exo.worker.engines.base can break src.exo.testkit.stub.engine, while a change to src.exo.testkit.stub.engine can't break src.exo.worker.engines.base.
Position
Below the diagonal: src.exo.testkit.stub.engine uses a module listed above it, which is the healthy direction.
src.exo.worker.runner.llm_inference.batch_generator uses src.exo.worker.disaggregated.server, so a change to src.exo.worker.disaggregated.server can break src.exo.worker.runner.llm_inference.batch_generator, while a change to src.exo.worker.runner.llm_inference.batch_generator can't break src.exo.worker.disaggregated.server.
Position
Below the diagonal: src.exo.worker.runner.llm_inference.batch_generator uses a module listed above it, which is the healthy direction.
src.exo.worker.runner.llm_inference.batch_generator uses src.exo.worker.engines.mlx.types, so a change to src.exo.worker.engines.mlx.types can break src.exo.worker.runner.llm_inference.batch_generator, while a change to src.exo.worker.runner.llm_inference.batch_generator can't break src.exo.worker.engines.mlx.types.
Position
Below the diagonal: src.exo.worker.runner.llm_inference.batch_generator uses a module listed above it, which is the healthy direction.
src.exo.worker.runner.llm_inference.batch_generator uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.worker.runner.llm_inference.batch_generator, while a change to src.exo.worker.runner.llm_inference.batch_generator can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.worker.runner.llm_inference.batch_generator uses a module listed above it, which is the healthy direction.
src.exo.worker.runner.llm_inference.batch_generator uses src.exo.shared.types.tasks, so a change to src.exo.shared.types.tasks can break src.exo.worker.runner.llm_inference.batch_generator, while a change to src.exo.worker.runner.llm_inference.batch_generator can't break src.exo.shared.types.tasks.
Position
Below the diagonal: src.exo.worker.runner.llm_inference.batch_generator uses a module listed above it, which is the healthy direction.
src.exo.worker.runner.llm_inference.batch_generator uses src.exo.worker.engines.base, so a change to src.exo.worker.engines.base can break src.exo.worker.runner.llm_inference.batch_generator, while a change to src.exo.worker.runner.llm_inference.batch_generator can't break src.exo.worker.engines.base.
Position
Below the diagonal: src.exo.worker.runner.llm_inference.batch_generator uses a module listed above it, which is the healthy direction.
src.exo.worker.serving uses src.exo.shared.types.common, so a change to src.exo.shared.types.common can break src.exo.worker.serving, while a change to src.exo.worker.serving can't break src.exo.shared.types.common.
Position
Below the diagonal: src.exo.worker.serving uses a module listed above it, which is the healthy direction.
src.exo.worker.serving uses src.exo.routing.membership, so a change to src.exo.routing.membership can break src.exo.worker.serving, while a change to src.exo.worker.serving can't break src.exo.routing.membership.
Position
Below the diagonal: src.exo.worker.serving uses a module listed above it, which is the healthy direction.
src.exo.worker.serving uses src.exo.shared.types.worker.instances, so a change to src.exo.shared.types.worker.instances can break src.exo.worker.serving, while a change to src.exo.worker.serving can't break src.exo.shared.types.worker.instances.
Position
Below the diagonal: src.exo.worker.serving uses a module listed above it, which is the healthy direction.
src.exo.worker.serving uses src.exo.worker.runner.supervisor, so a change to src.exo.worker.runner.supervisor can break src.exo.worker.serving, while a change to src.exo.worker.serving can't break src.exo.worker.runner.supervisor.
Position
Below the diagonal: src.exo.worker.serving uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 29% · Weak · gated by R2, R3, R7 ·
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 category
Findings
Severity
A03:2025 — Software Supply Chain Failures
70
High / Critical
A05:2025 — Injection
34
High / Critical
A07:2025 — Authentication Failures
4
High / Critical
Roadmap
Top priorities: Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
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 — 84
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 — 695
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 — 93
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
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 76 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 — 76 dimensions across the health lenses
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
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, 842 of 872 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.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
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 86 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 270 test source file(s) (.py, .swift, .rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT SCORED: this repository's production source includes .py, and the python executor ran against the .py half and did not finish re-running within its tier budget — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `npm ci --ignore-scripts` in dashboard/ (14 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python REDACTED/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `.typings/mlx/core/__init__.pyi`, `src/exo/api/adapters/chat_completions.py`, `src/exo/api/command_acceptance.py`, `src/exo/download/coordinator.py`, `src/exo/download/hub.py`, … (+20 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust, Svelte components, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust, Svelte components, Swift is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
R2 Cyclomatic Complexity — 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. 15 further occurrence(s) are not listed individually; the score already reflects all 55.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
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.
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.
63 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AppStore.sendMessage at 74. A further 2 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 apply.event_apply at 23 — 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: app/EXO/EXO/Views/MenuBarController.swift (MenuBarController.run 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.
+ 58 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with AppStore.sendMessage (cyclomatic 74). — Refactoring it lifts Cyclomatic Complexity from 6.3 to about 6.5/10.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 127 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 12 bodies over 60 down to 60 or less in Cognitive Complexity — start with responses.responses_request_to_text_generation (cognitive 111), AppStore.sendMessage (cognitive 105), encoding.render_message (cognitive 78). — 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 12 together lifts Cognitive Complexity from 4.2 to about 5.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.8 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 18 FileTooLong finding(s) in God Classes — start with model.py (3), REDACTED (2), app.svelte.ts. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 4 MethodTooLong finding(s) in God Classes — start with app.svelte.ts (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 TooManyMethods finding(s) in God Classes — start with app.svelte.ts, REDACTED, cluster.py. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
73 duplicated block group(s) detected. 5.0 % of the production lines (3,688 of 73,240) are in a reported copy. A further 40 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 10 of the 113 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.
Edited copy of a member (7 corresponding lines) · ×4src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1526
+ 80 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with model.py, sharding.py, adapter.py. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with model_cards.py, generate.py, batch_generate.py. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with REDACTED, encoding.py, sharding.py. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.4 / 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.
5 production modules (Cargo+npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
Off the main sequence: networking
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED, harness.py. — 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.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ 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.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 86 tests. Measured on the JavaScript/TypeScript suite only — at least 270 test source file(s) (.py, .swift, .rs) went unread, so its test quality is unmeasured and is not in these counts.
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.
10 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: blake3 · ×10
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
0 of 508 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 27 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python REDACTED/requirements.txt (pip/uv/Poetry) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: dashboard/src/routes/+page.svelte (32×50=1600); src/exo/master/main.py (19×35=665); dashboard/src/lib/stores/app.svelte.ts (8×74=592) Repeated repair below the complexity floor: src/exo/main.py (10 of 17 changes were fixes); src/exo/download/coordinator.py (3 of 5 changes were fixes); src/exo/shared/models/model_cards.py (3 of 5 changes were fixes)
Resolve the 16 Hotspot finding(s) in Churn × Complexity Hotspots — start with +page.svelte (2), REDACTED (2), app.svelte.ts. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with REDACTED, coordinator.py, model_cards.py. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.4 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
15 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/exo/worker/engines/image/pipeline/runner.py. Counted over 226 of the 387 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
45 deducted task-comment markers across 73240 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoComment · ×45src/exo/main.py:339
What to do
Resolve the 45 TodoComment finding(s) in Explicit Debt — start with utils_mlx.py (4), lib.rs (4), REDACTED (3). — One of this dimension's main actionable groups (45 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 of 1 documentation facets pass in full. 5 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
2 naming inconsistencies among 31 declarations measured against a convention their peers follow.
`uploadToPresignedUrl` spells `Url` where 14 names in the project spell it `URL`REDACTED:295
`UninstallEXO` spells `EXO` where 15 names in the project spell it `Exo`app/EXO/EXO/Views/Settings/UninstallEXO.swift:5
What to do
Resolve the 1 `uploadToPresignedUrl` spells `Url` where 14 names in the project spell… finding(s) in Naming Consistency — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 `UninstallEXO` spells `EXO` where 15 names in the project spell it `Exo` finding(s) in Naming Consistency — start with UninstallEXO.swift. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
doc comments repeat the namesdashboard/src/lib/stores/app.svelte.ts:1040
What to do
Resolve the 1 redundant comment finding(s) in Comment Value — start with app.svelte.ts. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D26 · Project Cohesion4.6 / 10Weak✓ Tool-verified
What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.
2 of 6 build units (Cargo, Python, Xcode, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
77 % of calls cross a namespace and 0 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
34 finding(s): 0 critical, 25 high, 5 medium, 4 low. 13 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 30 file(s) — `.typings/mlx/core/__init__.pyi` (line 1771, line 1772, line 1773, …), `packaging/dmg/create-dmg.sh` (line 16, line 17), `rust/exo_rs/src/logging.rs` (line 275), `rust/networking/src/membership.rs` (line 239), `src/exo/api/adapters/chat_completions.py`, … (+25 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 3 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
+ 8 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 13 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (14 issue-level, 1 of them charged here).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
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).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 18 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9), REDACTED (7), REDACTED (2). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 3 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
25 of 226 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is bench/prefill_decode_bench.py. Counted over 226 of the 387 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with prefill_decode_bench.py. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 24 Orphaned file finding(s) in Knowledge Freshness — start with wrappers.py (2), client.py (2), edit_adapter.py. — One of this dimension's main actionable groups (24 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with networking.rs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 7 Change coupling finding(s) in Change Coupling — start with ExoProcessController.swift, REDACTED, election.py. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with utils_mlx.py. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 22 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels5.3 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×7) — dashboard/src/lib/components/ChatForm.svelte:481, dashboard/src/lib/components/ChatSidebar.svelte:305, dashboard/src/lib/components/ImageParamsPanel.svelte:494, …
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×12) — dashboard/src/lib/components/ChatMessages.svelte:351, dashboard/src/lib/components/ChatSidebar.svelte:334, dashboard/src/lib/components/ImageParamsPanel.svelte:377, …
This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — dashboard/src/lib/components/ChatMessages.svelte:491, dashboard/src/lib/components/ImageLightbox.svelte:88
This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. — dashboard/src/lib/components/ChatModelSelector.svelte:294
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×2) — dashboard/src/lib/components/ModelPickerModal.svelte:1184, dashboard/src/routes/downloads/+page.svelte:855
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — dashboard/src/routes/+page.svelte:6292, dashboard/src/routes/downloads/+page.svelte:868
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0". (×4) — dashboard/src/lib/components/ChatMessages.svelte:406, dashboard/src/lib/components/ChatMessages.svelte:491, dashboard/src/lib/components/ImageLightbox.svelte:88, …
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — dashboard/src/lib/components/ModelFilterPopover.svelte:75, dashboard/src/routes/downloads/+page.svelte:861
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — dashboard/src/lib/components/ModelPickerModal.svelte:730, dashboard/src/lib/components/ModelPickerModal.svelte:1190
This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. (×2) — dashboard/src/lib/components/TokenHeatmap.svelte:152, dashboard/src/routes/+page.svelte:7455
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
<button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×4) — dashboard/src/lib/components/ChatForm.svelte:347, dashboard/src/lib/components/ImageParamsPanel.svelte:186, dashboard/src/lib/components/ImageParamsPanel.svelte:271, …
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×3) — dashboard/src/lib/components/ChatForm.svelte:481, dashboard/src/lib/components/ChatMessages.svelte:351, dashboard/src/lib/components/ImageParamsPanel.svelte:640
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×9) — dashboard/src/lib/components/ChatSidebar.svelte:305, dashboard/src/lib/components/ChatSidebar.svelte:334, dashboard/src/lib/components/ImageParamsPanel.svelte:377, …
`input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — dashboard/src/app.css:284
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
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.
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.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (Django/SQLAlchemy) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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.
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.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
P2 · Observability6.4 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 4/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `dashboard`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:5
`dashboard/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — dashboard/package.json:14
What to do
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — REDACTED:20
What to do
Pass `timeout=` on every `requests`/`httpx` call (requests has no default and will wait forever), mount an `HTTPAdapter(max_retries=Retry(...))` on shared sessions, and wrap calls to flaky dependencies in `tenacity` retries or a `pybreaker` circuit breaker.
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.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
9 duplicated blocks under dashboard/src/ have copies in at least two of the sibling directories lib, routes — 5 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — dashboard/src/lib/components/ModelCard.svelte:63
dashboard/src/lib/components/TopologyGraph.svelte:635 · dashboard/src/lib/components/TopologyGraph.svelte:718 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/components/TopologyGraph.svelte:635
dashboard/src/routes/traces/+page.svelte:77 · dashboard/src/routes/traces/[taskId]/+page.svelte:79 — the two spans are one implementation copied and then locally edited — 236 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — dashboard/src/routes/traces/+page.svelte:77
dashboard/src/lib/stores/app.svelte.ts:3258 · dashboard/src/lib/stores/app.svelte.ts:3507 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:3258
dashboard/src/lib/components/ModelCard.svelte:63 · dashboard/src/routes/+page.svelte:1359 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/components/ModelCard.svelte:63
dashboard/src/lib/stores/app.svelte.ts:1339 · dashboard/src/lib/stores/app.svelte.ts:1426 — 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. — dashboard/src/lib/stores/app.svelte.ts:1339
dashboard/src/lib/components/TopologyGraph.svelte:1043 · dashboard/src/lib/components/TopologyGraph.svelte:1118 — 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. — dashboard/src/lib/components/TopologyGraph.svelte:1043
dashboard/src/lib/stores/app.svelte.ts:2019 · dashboard/src/lib/stores/app.svelte.ts:2237 — 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. — dashboard/src/lib/stores/app.svelte.ts:2019
dashboard/src/lib/stores/app.svelte.ts:2081 · dashboard/src/lib/stores/app.svelte.ts:2286 · dashboard/src/lib/stores/app.svelte.ts:2905 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — dashboard/src/lib/stores/app.svelte.ts:2081
dashboard/src/lib/stores/app.svelte.ts:3149 · dashboard/src/lib/stores/app.svelte.ts:3435 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:3149
dashboard/src/routes/+page.svelte:1036 · dashboard/src/routes/+page.svelte:4281 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/routes/+page.svelte:1036
dashboard/src/lib/stores/app.svelte.ts:2660 · dashboard/src/lib/stores/app.svelte.ts:3045 · dashboard/src/lib/stores/app.svelte.ts:3322 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:2660
dashboard/src/lib/stores/app.svelte.ts:1972 · dashboard/src/lib/stores/app.svelte.ts:2765 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:1972
dashboard/src/lib/stores/app.svelte.ts:3596 · dashboard/src/lib/stores/app.svelte.ts:3621 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:3596
dashboard/src/lib/components/ChatAttachments.svelte:18 · dashboard/src/lib/components/ChatMessages.svelte:140 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/components/ChatAttachments.svelte:18
dashboard/src/routes/+page.svelte:597 · dashboard/src/routes/+page.svelte:633 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/routes/+page.svelte:597
dashboard/src/lib/stores/app.svelte.ts:1998 · dashboard/src/lib/stores/app.svelte.ts:2214 — 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. — dashboard/src/lib/stores/app.svelte.ts:1998
dashboard/src/lib/components/ChatSidebar.svelte:197 · dashboard/src/lib/stores/app.svelte.ts:1195 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — dashboard/src/lib/components/ChatSidebar.svelte:197
dashboard/src/lib/components/MarkdownContent.svelte:174 · dashboard/src/lib/components/MarkdownContent.svelte:191 — 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. — dashboard/src/lib/components/MarkdownContent.svelte:174
dashboard/src/lib/components/ModelCard.svelte:413 · dashboard/src/lib/components/TopologyGraph.svelte:457 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/src/lib/components/ModelCard.svelte:413
dashboard/src/lib/components/ChatMessages.svelte:205 · dashboard/src/lib/components/ChatSidebar.svelte:71 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — dashboard/src/lib/components/ChatMessages.svelte:205
dashboard/src/lib/components/TopologyGraph.svelte:1077 · dashboard/src/lib/components/TopologyGraph.svelte:1110 — 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. — dashboard/src/lib/components/TopologyGraph.svelte:1077
dashboard/src/lib/components/TopologyGraph.svelte:1163 · dashboard/src/lib/components/TopologyGraph.svelte:1181 — 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. — dashboard/src/lib/components/TopologyGraph.svelte:1163
dashboard/src/lib/stores/app.svelte.ts:3026 · dashboard/src/lib/stores/app.svelte.ts:3302 — 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. — dashboard/src/lib/stores/app.svelte.ts:3026
dashboard/src/lib/stores/app.svelte.ts:3128 · dashboard/src/lib/stores/app.svelte.ts:3415 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:3128
dashboard/src/lib/stores/app.svelte.ts:2325 · dashboard/src/lib/stores/app.svelte.ts:2971 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:2325
dashboard/src/lib/components/ImageParamsPanel.svelte:116 · dashboard/src/lib/components/ImageParamsPanel.svelte:133 — 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. — dashboard/src/lib/components/ImageParamsPanel.svelte:116
dashboard/src/lib/components/MarkdownContent.svelte:246 · dashboard/src/lib/components/MarkdownContent.svelte:258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — dashboard/src/lib/components/MarkdownContent.svelte:246
dashboard/src/lib/components/MarkdownContent.svelte:423 · dashboard/src/lib/components/MarkdownContent.svelte:449 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/components/MarkdownContent.svelte:423
dashboard/src/lib/components/TopologyGraph.svelte:47 · dashboard/src/routes/+page.svelte:3102 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/components/TopologyGraph.svelte:47
dashboard/src/lib/stores/app.svelte.ts:2728 · dashboard/src/lib/stores/app.svelte.ts:2756 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:2728
dashboard/src/routes/+page.svelte:296 · dashboard/src/routes/+page.svelte:314 — 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. — dashboard/src/routes/+page.svelte:296
dashboard/src/routes/+page.svelte:1120 · dashboard/src/routes/+page.svelte:1136 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/routes/+page.svelte:1120
dashboard/src/lib/components/TopologyGraph.svelte:988 · dashboard/src/lib/components/TopologyGraph.svelte:1001 — 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. — dashboard/src/lib/components/TopologyGraph.svelte:988
dashboard/src/lib/stores/app.svelte.ts:2223 · dashboard/src/lib/stores/app.svelte.ts:2821 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/lib/stores/app.svelte.ts:2223
dashboard/src/routes/+page.svelte:3899 · dashboard/src/routes/+page.svelte:4083 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — dashboard/src/routes/+page.svelte:3899
dashboard/src/lib/components/ChatMessages.svelte:115 · dashboard/src/lib/components/ChatMessages.svelte:171 · dashboard/src/lib/components/ModelPickerModal.svelte:676 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — dashboard/src/lib/components/ChatMessages.svelte:115
dashboard/src/lib/components/TopologyGraph.svelte:894 · dashboard/src/lib/components/TopologyGraph.svelte:908 — 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. — dashboard/src/lib/components/TopologyGraph.svelte:894
dashboard/src/routes/+page.svelte:3323 · dashboard/src/routes/downloads/+page.svelte:116 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — dashboard/src/routes/+page.svelte:3323
dashboard/src/routes/downloads/+page.svelte:105 · dashboard/src/routes/downloads/+page.svelte:127 · dashboard/src/routes/traces/+page.svelte:60 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — dashboard/src/routes/downloads/+page.svelte:105
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
(anonymous) has cyclomatic complexity 65 and cognitive complexity 103; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/components/TopologyGraph.svelte:529
collectDownloadStatus has cyclomatic complexity 50 and cognitive complexity 86; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:2100
(anonymous) has cyclomatic complexity 42 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/downloads/+page.svelte:233
estimateMemoryGB has cyclomatic complexity 42 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — dashboard/src/lib/components/ModelCard.svelte:67, dashboard/src/routes/+page.svelte:1363
(anonymous) has cyclomatic complexity 35 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:3493
transformTopology has cyclomatic complexity 33 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:475
estimatePerformance has cyclomatic complexity 32 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:1439
handleAutoSend has cyclomatic complexity 31 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:3930
sendMessage has cyclomatic complexity 31 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:2573
deriveInstanceStatus has cyclomatic complexity 29 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:2756
editImage has cyclomatic complexity 29 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:3297
generateImage has cyclomatic complexity 27 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:3025
parseSSEStream has cyclomatic complexity 24 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:2421
(anonymous) has cyclomatic complexity 24 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:2698
parseDownloadProgress has cyclomatic complexity 22 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:2037
totalDownload has cyclomatic complexity 20 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/utils/download_progress.ts:51
fetchState has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:1577
extractModelCard has cyclomatic complexity 19 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/downloads/+page.svelte:158
(anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:276
(anonymous) has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/components/ModelPickerModal.svelte:407
getInstanceConnections has cyclomatic complexity 16 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:3216
refreshConversationModelFromInstances has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:1281
(anonymous) has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:3636
indexModelDownloads has cyclomatic complexity 15 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/utils/downloads.ts:173
transformNetworkInterface has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:441
getConnectionInfo has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/components/ModelCard.svelte:432
renderGraph has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/components/TopologyGraph.svelte:169
(anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/components/TopologyGraph.svelte:330
getInterfaceForIp has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/components/ModelCard.svelte:372
observe has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/utils/download_activity.ts:40
resolveConversationInfo has cyclomatic complexity 14 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/components/ChatSidebar.svelte:223
modelStateOnNode has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/utils/downloads.ts:233
getArrow has cyclomatic complexity 13 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/components/TopologyGraph.svelte:452
(anonymous) has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:2858
(anonymous) has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:3051
getRunnerFailures has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:2594
(anonymous) has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/routes/+page.svelte:4232
(anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/stores/app.svelte.ts:2041
parseDeployments has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — dashboard/src/lib/utils/deployments.ts:109
Do you agree with this assessment?
R3 · Large Files0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
dashboard/src/routes/+page.svelte has 7918 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/routes/+page.svelte:1
dashboard/src/lib/stores/app.svelte.ts has 3557 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/stores/app.svelte.ts:1
dashboard/src/lib/components/ModelPickerModal.svelte has 1198 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/ModelPickerModal.svelte:1
dashboard/src/lib/components/TopologyGraph.svelte has 1152 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/TopologyGraph.svelte:1
dashboard/src/lib/components/ModelCard.svelte has 1037 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/ModelCard.svelte:1
dashboard/src/routes/downloads/+page.svelte has 956 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/routes/downloads/+page.svelte:1
dashboard/src/lib/components/MarkdownContent.svelte has 947 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/MarkdownContent.svelte:1
dashboard/src/lib/components/ChatMessages.svelte has 830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/ChatMessages.svelte:1
dashboard/src/lib/components/ModelPickerGroup.svelte has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/ModelPickerGroup.svelte:1
dashboard/src/routes/integrations/+page.svelte has 655 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/routes/integrations/+page.svelte:1
dashboard/src/lib/components/ImageParamsPanel.svelte has 644 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/ImageParamsPanel.svelte:1
dashboard/src/lib/components/ChatSidebar.svelte has 588 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/ChatSidebar.svelte:1
dashboard/src/lib/components/ChatForm.svelte has 560 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/ChatForm.svelte:1
dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage2.2 / 10Critical✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×39) — dashboard/src/routes/+page.svelte:1, dashboard/src/lib/stores/app.svelte.ts:1, dashboard/src/lib/components/TopologyGraph.svelte:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 8 application, 3 tooling and 14 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×14) — dashboard/src/lib/stores/app.svelte.ts, dashboard/src/lib/types/files.ts, dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte, …
no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×8) — dashboard/src/lib/components/TopologyGraph.svelte, dashboard/src/lib/components/ModelPickerModal.svelte, dashboard/src/lib/components/ModelCard.svelte, …
no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ChatMessages.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dashboard/src/lib/components/MarkdownContent.svelte
no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ChatForm.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — dashboard/src/lib/components/ImageParamsPanel.svelte, dashboard/src/lib/components/ChatAttachments.svelte
no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ModelPickerModal.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×4) — dashboard/src/lib/components/ModelPickerGroup.svelte, dashboard/src/lib/components/ModelFilterPopover.svelte, dashboard/src/lib/components/HuggingFaceResultItem.svelte, …
no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/ChatMessages.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×3) — dashboard/src/lib/components/TokenHeatmap.svelte, dashboard/src/lib/components/ImageLightbox.svelte, dashboard/src/lib/components/PrefillProgressBar.svelte
no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/FamilySidebar.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — dashboard/src/lib/components/FamilyLogos.svelte
Nothing imports this binding — it is safe to review for removal. (×5) — dashboard/src/lib/utils/api_errors.ts:23, dashboard/src/lib/utils/downloads.ts:92, dashboard/src/lib/utils/downloads.ts:109, …
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. — dashboard/src/routes/+page.svelte:3083
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in dashboard/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
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.
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 3/19 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`fetchFeatureFlags` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:1567
`fetchState` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:1577
`fetchPlacementPreviews` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:1650
`regenerateFromToken` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:1918
`regenerateChatCompletion` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:2148
`startModelDownload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3579
`startDownload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3596
`cancelDownload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3621
`createInstanceLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3643
`updateInstanceLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3662
`deleteInstanceLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3685
`deleteDownload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3700
`listTraces` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3720
`checkTraceExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3731
`fetchTraceStats` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3743
`deleteTraces` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — dashboard/src/lib/stores/app.svelte.ts:3756
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
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.
`except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×10) — tools/src/exo_tools/harness.py:465, src/exo/worker/runner/supervisor.py:807, src/exo/worker/runner/llm_inference/tool_parsers.py:75, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×17) — tools/src/exo_tools/harness.py:569, src/exo/worker/disaggregated/server.py:50, dashboard/src/routes/+page.svelte:255, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×2) — dashboard/src/routes/+page.svelte:815, dashboard/src/routes/+page.svelte:3602
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — REDACTED:290
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`info` at line 127 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog. — tools/src/exo_tools/cluster.py:127
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
Unscored — 2 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.
X10 Duplicated predicate — 21 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 48 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — AX6 reached only 28% of this repository's production lines — python (55,197 lines), swift (7,010 lines), rust (5,520 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (exo), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
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) — 25 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the node:test suite in dashboard/ ran and not one test passed (throw new ERR_UNKNOWN_FILE_EXTENSION(ext, filepath);), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a pytest-benchmark or pytest-codspeed dependency with tests taking the `benchmark` fixture, an asv.conf.json with its `time_`/`mem_`/`peakmem_` benchmarks, or a pyperf Runner, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 28% of this repository's production lines — python (55,197 lines), swift (7,010 lines), rust (5,520 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — 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 — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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
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
X29 Per-element action decided by a fixed element — X29 reached only 34% of this repository's production lines — python (55,197 lines), swift (7,010 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC2 · Forms & labels· <input> without a programmatic label · ×12
<input> without a programmatic label dashboard/src/lib/components/ChatSidebar.svelte:305— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label dashboard/src/lib/components/ChatSidebar.svelte:334— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label dashboard/src/lib/components/ImageParamsPanel.svelte:377— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label dashboard/src/lib/components/ImageParamsPanel.svelte:414— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label dashboard/src/lib/components/ImageParamsPanel.svelte:494— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label dashboard/src/lib/components/ImageParamsPanel.svelte:511— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label dashboard/src/lib/components/ImageParamsPanel.svelte:555— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label dashboard/src/lib/components/ImageParamsPanel.svelte:599— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label dashboard/src/lib/components/ModelPickerModal.svelte:753— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label dashboard/src/lib/components/ModelPickerModal.svelte:780— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label dashboard/src/lib/components/ModelPickerModal.svelte:929— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<input> without a programmatic label dashboard/src/routes/integrations/+page.svelte:555— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <select> without a programmatic label · ×4
<select> without a programmatic label dashboard/src/routes/integrations/+page.svelte:501— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label dashboard/src/routes/integrations/+page.svelte:543— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label dashboard/src/routes/integrations/+page.svelte:582— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label dashboard/src/routes/integrations/+page.svelte:609— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <textarea> without a programmatic label · ×3
<textarea> without a programmatic label dashboard/src/lib/components/ChatForm.svelte:481— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
<textarea> without a programmatic label dashboard/src/lib/components/ChatMessages.svelte:351— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<textarea> without a programmatic label dashboard/src/lib/components/ImageParamsPanel.svelte:640— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <img> · ×3
Click handler on a non-interactive <img> dashboard/src/lib/components/ChatMessages.svelte:406— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <img> dashboard/src/lib/components/ChatMessages.svelte:491— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Click handler on a non-interactive <img> dashboard/src/lib/components/ImageLightbox.svelte:88— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
AC2 · Forms & labels· Custom control with no accessible name on <img> · ×2
Custom control with no accessible name on <img> dashboard/src/lib/components/ChatMessages.svelte:491— This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <img> dashboard/src/lib/components/ImageLightbox.svelte:88— This <img> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×2
Custom control with no accessible name on <div> dashboard/src/lib/components/ModelPickerModal.svelte:1184— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> dashboard/src/routes/downloads/+page.svelte:855— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics· Hover-only interaction on <div> · ×2
Hover-only interaction on <div> dashboard/src/lib/components/TokenHeatmap.svelte:152— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
Hover-only interaction on <div> dashboard/src/routes/+page.svelte:7455— This <div> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus.
D30 · Dependency Vulnerabilities· High vulnerability · ×2
REDACTED
REDACTED
AC2 · Forms & labels· Custom control with no accessible name on <span> · ×1
Custom control with no accessible name on <span> dashboard/src/lib/components/ChatModelSelector.svelte:294— This <span> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> dashboard/src/routes/traces/+page.svelte:247— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Orphaned knowledge bench/prefill_decode_bench.py:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Boundary-crossing change coupling: networking.rs ↔ router.py rust/exo_rs/src/networking.rs:1— `rust/exo_rs/src/networking.rs` (context rust) and `src/exo/routing/router.py` (context exo) sit in DIFFERENT parts of the tree yet 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) — 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 `d7f5db76` Connect only to nodes of the same build, and say so when one isn't (#…; `bc9d09d3` fix(networking): one stalled node no longer freezes event delivery to…; `2da740c3` Feat/static peer discovery (#1690) (at that commit the file was still `rust/exo_pyo3_bindings/src/networking.rs`) — run `git show` on any of them.
TodoComment src/exo/main.py:339— # TODO: This function needs refactoring generally — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/main.py:474— # TODO: Refactor the current verbosity system — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/tests/unittests/conftest.py:36— # TODO: Is this actually better than using Mock/Fake dataclasses? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/runner/diagnostics.py:91— # TODO: Eventually this will become a stateful parser with a more advanced architecture, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/runner/supervisor.py:185— # TODO: in the future use [Drain3](https://github.com/logpai/Drain3)
TodoComment src/exo/worker/runner/llm_inference/tool_parsers.py:247— # TODO / example code: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/constants.py:1— # TODO: Do we want so many constants? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/constants.py:16— # TODO: We should really make this opt-in, but Kimi requires trust_remote_code=True — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/utils_mlx.py:116— # TODO: singleton instances — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/utils_mlx.py:218— # TODO: pass in seed from params — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/utils_mlx.py:314— # TODO: See if we should quantize the model. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/utils_mlx.py:349— # TODO: Do we need this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/vision.py:136— # TODO: Update if we add torch vision. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/generator/generate.py:310— # TODO(evan): kill the callbacks/runner refactor — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/mlx/generator/generate.py:550— # TODO: Randomise task seed and set in taskparams, instead of hard coding as 42. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/image/builder.py:189— # todo: yield CancelledResponse properly — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/image/distributed_model.py:68— # TODO(ciaran): Do we need this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/image/pipeline/runner.py:339— # TODO(ciaran): try to remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/image/models/base.py:244— # TODO(ciaran): — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/image/models/qwen/adapter.py:132— # TODO(ciaran): currently None but maybe we will deduplicate with edit — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/worker/engines/image/models/qwen/edit_adapter.py:297— # TODO(ciaran): config is untyped and unused, unsure if Config or RuntimeConfig is intended — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/utils/async_process.py:195— # TODO: maybe in the future if needed, create stdin that is also installed, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/utils/info_gatherer/net_profile.py:26— # TODO: use real IpAddress types — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/utils/info_gatherer/system_info.py:140— # TODO: better non mac support — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/exo/shared/apply.py:195— # TODO(ciaran): deduplicate by model_id for now. Will need to use — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
+ 20 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×39
No test reaches this file dashboard/src/routes/+page.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/stores/app.svelte.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/TopologyGraph.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ModelPickerModal.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/MarkdownContent.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/routes/downloads/+page.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ModelCard.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/routes/integrations/+page.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/types/files.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ChatForm.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ChatSidebar.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ChatMessages.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ChatModelSelector.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ImageParamsPanel.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ModelPickerGroup.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/routes/traces/[taskId]/+page.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/routes/traces/+page.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/TokenHeatmap.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/DeviceIcon.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/stores/toast.svelte.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/stores/favorites.svelte.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/stores/recents.svelte.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/ModelFilterPopover.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file dashboard/src/lib/components/HeaderNav.svelte:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
+ 14 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×19
Swallowed exception (empty catch) tools/src/exo_tools/harness.py:569— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/exo/worker/disaggregated/server.py:50— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/+page.svelte:255— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/+page.svelte:811— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/+page.svelte:815— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/+page.svelte:1772— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/+page.svelte:1893— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/+page.svelte:3457— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/+page.svelte:3602— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/integrations/+page.svelte:395— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/routes/downloads/+page.svelte:213— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/lib/utils/api_errors.ts:28— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/lib/utils/clipboard.ts:10— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/lib/stores/app.svelte.ts:791— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/lib/stores/app.svelte.ts:1148— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/lib/stores/app.svelte.ts:1572— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/lib/stores/app.svelte.ts:2456— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/lib/stores/app.svelte.ts:2474— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) dashboard/src/lib/stores/app.svelte.ts:2491— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
FileTooLong: stores/app.svelte.ts dashboard/src/lib/stores/app.svelte.ts— FileTooLong — 2531 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: AppStore (620-3776). The bar is 500 significant lines; this is 2031 over it, 5.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 2011 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1511 over it, 4.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: deepseek_v4/model.py src/exo/worker/engines/mlx/models/deepseek_v4/model.py— FileTooLong — 1902 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1402 over it, 3.80× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: deepseek_v41/model.py src/exo/worker/engines/mlx/models/deepseek_v41/model.py— FileTooLong — 1319 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 819 over it, 2.64× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: testkit/cluster.py src/exo/testkit/cluster.py— FileTooLong — 990 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 490 over it, 1.98× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: pipeline/runner.py src/exo/worker/engines/image/pipeline/runner.py— FileTooLong — 935 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 435 over it, 1.87× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: qwen3/qwen4_exp.py src/exo/worker/engines/mlx/models/qwen3/qwen4_exp.py— FileTooLong — 901 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 401 over it, 1.80× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: deepseek_v41/encoding.py src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py— FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 213 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: glm/glm5_next.py src/exo/worker/engines/mlx/models/glm/glm5_next.py— FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 168 over it, 1.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mlx/vision.py src/exo/worker/engines/mlx/vision.py— FileTooLong — 649 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 149 over it, 1.30× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: adapters/responses.py src/exo/api/adapters/responses.py— FileTooLong — 629 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 129 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: runner/supervisor.py src/exo/worker/runner/supervisor.py— FileTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 118 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: generator/generate.py src/exo/worker/engines/mlx/generator/generate.py— FileTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 107 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: mlx/utils_mlx.py src/exo/worker/engines/mlx/utils_mlx.py— FileTooLong — 606 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 106 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: inkling/model.py src/exo/worker/engines/mlx/models/inkling/model.py— FileTooLong — 587 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 87 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: shared/apply.py src/exo/shared/apply.py— FileTooLong — 523 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 23 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: exo/main.py src/exo/main.py— FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 17 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: llm_inference/batch_generator.py src/exo/worker/runner/llm_inference/batch_generator.py— FileTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 11 over it, 1.02× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Focus outline removed inline dashboard/src/lib/components/ChatForm.svelte:347— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ChatForm.svelte:481— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ChatMessages.svelte:351— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ChatSidebar.svelte:305— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ChatSidebar.svelte:334— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ImageParamsPanel.svelte:186— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ImageParamsPanel.svelte:271— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ImageParamsPanel.svelte:377— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ImageParamsPanel.svelte:414— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ImageParamsPanel.svelte:494— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ImageParamsPanel.svelte:640— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ModelPickerModal.svelte:753— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ModelPickerModal.svelte:780— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/lib/components/ModelPickerModal.svelte:929— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/routes/+page.svelte:7126— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline dashboard/src/routes/integrations/+page.svelte:555— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Hotspot: dashboard/src/routes/+page.svelte dashboard/src/routes/+page.svelte:2100— dashboard/src/routes/+page.svelte changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in collectDownloadStatus at line 2100. 26 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- dashboard/src/routes/+page.svelte`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/master/main.py src/exo/master/main.py:214— src/exo/master/main.py changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in Master._command_processor at line 214. 9 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/master/main.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: dashboard/src/lib/stores/app.svelte.ts dashboard/src/lib/stores/app.svelte.ts:2573— dashboard/src/lib/stores/app.svelte.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 74 in AppStore.sendMessage at line 2573. 7 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- dashboard/src/lib/stores/app.svelte.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/master/placement.py src/exo/master/placement.py:298— src/exo/master/placement.py changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in placement.place_instance at line 298. 4 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/master/placement.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/worker/main.py src/exo/worker/main.py:308— src/exo/worker/main.py changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Worker.plan_step at line 308. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/worker/main.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/worker/engines/mlx/generator/generate.py src/exo/worker/engines/mlx/generator/generate.py:535— src/exo/worker/engines/mlx/generator/generate.py changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 50 in generate.mlx_generate at line 535. 3 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/worker/engines/mlx/generator/generate.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: dashboard/src/routes/downloads/+page.svelte dashboard/src/routes/downloads/+page.svelte:233— dashboard/src/routes/downloads/+page.svelte changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in (anonymous) at line 233. 4 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- dashboard/src/routes/downloads/+page.svelte`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/worker/runner/supervisor.py src/exo/worker/runner/supervisor.py:779— src/exo/worker/runner/supervisor.py changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in RunnerSupervisor._check_runner at line 779. 9 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/worker/runner/supervisor.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/worker/engines/mlx/utils_mlx.py src/exo/worker/engines/mlx/utils_mlx.py:585— src/exo/worker/engines/mlx/utils_mlx.py changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in utils_mlx.render_chat_template at line 585. 4 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/worker/engines/mlx/utils_mlx.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: dashboard/src/lib/components/TopologyGraph.svelte dashboard/src/lib/components/TopologyGraph.svelte:529— dashboard/src/lib/components/TopologyGraph.svelte changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 65 in (anonymous) at line 529. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- dashboard/src/lib/components/TopologyGraph.svelte`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/networking/src/swarm.rs rust/networking/src/swarm.rs:212— rust/networking/src/swarm.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in networking::swarm::drive_membership at line 212. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- rust/networking/src/swarm.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: rust/networking/src/discovery.rs rust/networking/src/discovery.rs:189— rust/networking/src/discovery.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Discovery::respond at line 189. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- rust/networking/src/discovery.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/worker/engines/mlx/generator/batch_generate.py src/exo/worker/engines/mlx/generator/batch_generate.py:127— src/exo/worker/engines/mlx/generator/batch_generate.py changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in ExoBatchGenerator.submit at line 127. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/worker/engines/mlx/generator/batch_generate.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/worker/engines/mlx/sharding/pipeline.py src/exo/worker/engines/mlx/sharding/pipeline.py:100— src/exo/worker/engines/mlx/sharding/pipeline.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in PipelineLastLayer.__call__ at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/worker/engines/mlx/sharding/pipeline.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/api/adapters/claude.py src/exo/api/adapters/claude.py:348— src/exo/api/adapters/claude.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in claude.generate_claude_stream at line 348. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/api/adapters/claude.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/exo/routing/event_router.py src/exo/routing/event_router.py:160— src/exo/routing/event_router.py changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in EventRouter._run_ext_in at line 160. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/routing/event_router.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
X2 · Cancellation propagation· Async function without AbortSignal · ×16
Async function without AbortSignal: fetchFeatureFlags dashboard/src/lib/stores/app.svelte.ts:1567— `fetchFeatureFlags` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchState dashboard/src/lib/stores/app.svelte.ts:1577— `fetchState` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchPlacementPreviews dashboard/src/lib/stores/app.svelte.ts:1650— `fetchPlacementPreviews` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: regenerateFromToken dashboard/src/lib/stores/app.svelte.ts:1918— `regenerateFromToken` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: regenerateChatCompletion dashboard/src/lib/stores/app.svelte.ts:2148— `regenerateChatCompletion` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: startModelDownload dashboard/src/lib/stores/app.svelte.ts:3579— `startModelDownload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: startDownload dashboard/src/lib/stores/app.svelte.ts:3596— `startDownload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: cancelDownload dashboard/src/lib/stores/app.svelte.ts:3621— `cancelDownload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: createInstanceLink dashboard/src/lib/stores/app.svelte.ts:3643— `createInstanceLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: updateInstanceLink dashboard/src/lib/stores/app.svelte.ts:3662— `updateInstanceLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: deleteInstanceLink dashboard/src/lib/stores/app.svelte.ts:3685— `deleteInstanceLink` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: deleteDownload dashboard/src/lib/stores/app.svelte.ts:3700— `deleteDownload` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: listTraces dashboard/src/lib/stores/app.svelte.ts:3720— `listTraces` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: checkTraceExists dashboard/src/lib/stores/app.svelte.ts:3731— `checkTraceExists` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchTraceStats dashboard/src/lib/stores/app.svelte.ts:3743— `fetchTraceStats` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: deleteTraces dashboard/src/lib/stores/app.svelte.ts:3756— `deleteTraces` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Swallowed exception (caught, then discarded) tools/src/exo_tools/harness.py:465— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/worker/runner/supervisor.py:807— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/worker/runner/llm_inference/tool_parsers.py:75— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/worker/runner/llm_inference/tool_parsers.py:99— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/worker/runner/llm_inference/tool_parsers.py:237— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/worker/runner/llm_inference/tool_parsers.py:259— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:599— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:204— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/utils/info_gatherer/info_gatherer.py:369— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) src/exo/shared/models/model_cards.py:129— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:290— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×9
Change coupling: ExoProcessController.swift ↔ SettingsView.swift app/EXO/EXO/ExoProcessController.swift:1— `app/EXO/EXO/ExoProcessController.swift` and `app/EXO/EXO/Views/SettingsView.swift` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e50a8d32` app: keep models on uninstall by default, add https:// to the HF endp…; `b58554da` app: settings for launch at login and opening the dashboard on startu…; `ccaae3e0` app: bind env-var rows by id and never save or pass invalid names (#2… — run `git show` on any of them.
Change coupling: REDACTED ↔ commands.py src/exo/main.py:1— `src/exo/main.py` and `src/exo/shared/types/commands.py` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `aacc322b` Launched models survive a change of master, a heal and a full restart…; `591c5981` fix: keep running models through a change of master (#2369); `dc8d42b4` add system ids (#1536) — run `git show` on any of them.
Change coupling: election.py ↔ REDACTED src/exo/shared/election.py:1— `src/exo/shared/election.py` and `src/exo/worker/main.py` 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `61d2a2b6` add lazy task group (#1569); `572e6479` better cancellation (#1388); `880a18d2` fix disconnects — run `git show` on any of them.
Change coupling: claude.py ↔ generate.py src/exo/api/adapters/claude.py:1— `src/exo/api/adapters/claude.py` and `src/exo/worker/engines/mlx/generator/generate.py` 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) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `87d9b69f` Refuse a request the model can't take, before any work on it (#2563); `abd75ae0` Truncate long logs with repr (#1854); `025ed9fd` feat: add prefill progress bar for long prompts (#1181) (at that commit the file was still `src/exo/master/adapters/claude.py`) — run `git show` on any of them.
Change coupling: commands.py ↔ events.py src/exo/shared/types/commands.py:1— `src/exo/shared/types/commands.py` and `src/exo/shared/types/events.py` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `aacc322b` Launched models survive a change of master, a heal and a full restart…; `f9bd74aa` Say why every instance is removed, and tell its requests the real rea…; `49951e1b` Sync custom model cards across nodes (#1768) — run `git show` on any of them.
Change coupling: chat_completions.py ↔ generate.py src/exo/api/adapters/chat_completions.py:1— `src/exo/api/adapters/chat_completions.py` and `src/exo/worker/engines/mlx/generator/generate.py` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `87d9b69f` Refuse a request the model can't take, before any work on it (#2563); `abd75ae0` Truncate long logs with repr (#1854); `7df3774c` Improve batch performance and stats reporting (#1777) — run `git show` on any of them.
Change coupling: EXOApp.swift ↔ NetworkSetupHelper.swift app/EXO/EXO/EXOApp.swift:1— `app/EXO/EXO/EXOApp.swift` and `app/EXO/EXO/Services/NetworkSetupHelper.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `7d2a97db` app: start quietly: nothing opens at login, no prompts at launch (#2492); `3a9baeb9` EXO: add CLI flags for root install/uninstall; `ffacabe7` Fix uninstall button error (#1306) — run `git show` on any of them.
Duplicated block (12 lines × 2 locations) dashboard/src/lib/components/ImageParamsPanel.svelte:116— dashboard/src/lib/components/ImageParamsPanel.svelte:116 · dashboard/src/lib/components/ImageParamsPanel.svelte:133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2 locations) dashboard/src/lib/components/MarkdownContent.svelte:246— dashboard/src/lib/components/MarkdownContent.svelte:246 · dashboard/src/lib/components/MarkdownContent.svelte:258 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2 locations) dashboard/src/lib/components/MarkdownContent.svelte:423— dashboard/src/lib/components/MarkdownContent.svelte:423 · dashboard/src/lib/components/MarkdownContent.svelte:449 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) dashboard/src/lib/components/TopologyGraph.svelte:47— dashboard/src/lib/components/TopologyGraph.svelte:47 · dashboard/src/routes/+page.svelte:3102 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:2728— dashboard/src/lib/stores/app.svelte.ts:2728 · dashboard/src/lib/stores/app.svelte.ts:2756 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (12 lines × 2 locations) dashboard/src/routes/+page.svelte:296— dashboard/src/routes/+page.svelte:296 · dashboard/src/routes/+page.svelte:314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2 locations) dashboard/src/routes/+page.svelte:1120— dashboard/src/routes/+page.svelte:1120 · dashboard/src/routes/+page.svelte:1136 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×4
Modal dialog does not manage focus dashboard/src/lib/components/ModelFilterPopover.svelte:75— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus dashboard/src/lib/components/ModelPickerModal.svelte:730— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus dashboard/src/lib/components/ModelPickerModal.svelte:1190— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus dashboard/src/routes/downloads/+page.svelte:861— This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
MethodTooLong: AppStore.generateImage dashboard/src/lib/stores/app.svelte.ts:3025— MethodTooLong — generateImage runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AppStore.editImage dashboard/src/lib/stores/app.svelte.ts:3297— MethodTooLong — editImage runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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: AppStore.regenerateFromToken dashboard/src/lib/stores/app.svelte.ts:1918— MethodTooLong — regenerateFromToken runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× 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: AppStore.regenerateChatCompletion dashboard/src/lib/stores/app.svelte.ts:2148— MethodTooLong — regenerateChatCompletion runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×4
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1526— src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1526-1532 | src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1619-1636 — 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) src/exo/worker/engines/mlx/models/flint/sharding.py:68— src/exo/worker/engines/mlx/models/flint/sharding.py:68-74 | src/exo/worker/engines/mlx/models/laguna/sharding.py:72-86 — 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) src/exo/worker/engines/image/models/flux/adapter.py:86— src/exo/worker/engines/image/models/flux/adapter.py:86-92 | src/exo/worker/engines/image/models/qwen/adapter.py:177-183 — 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) src/exo/worker/engines/mlx/models/inkling/reasoning.py:20— src/exo/worker/engines/mlx/models/inkling/reasoning.py:20-26 | src/exo/worker/engines/mlx/models/minimax/reasoning.py:32-42 — 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.
Duplicated block (11 lines × 2) src/exo/shared/models/model_cards.py:374— src/exo/shared/models/model_cards.py:374-384 | src/exo/shared/models/model_cards.py:398-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) src/exo/worker/engines/image/generate.py:128— src/exo/worker/engines/image/generate.py:128-138 | src/exo/worker/engines/image/generate.py:177-187 — 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 `src/exo/worker/engines/image/generate.py:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/exo/worker/engines/mlx/generator/batch_generate.py:295— src/exo/worker/engines/mlx/generator/batch_generate.py:295-305 | src/exo/worker/engines/mlx/generator/generate.py:606-616 — 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) src/exo/worker/engines/image/models/qwen/adapter.py:292— src/exo/worker/engines/image/models/qwen/adapter.py:292-302 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:385-395 — before extracting anything, compare `src/exo/worker/engines/image/models/qwen/adapter.py` and `src/exo/worker/engines/image/models/qwen/edit_adapter.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) REDACTED:79— REDACTED:79-88 | REDACTED:96-105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:778— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:778-787 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:1014-1023 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:778` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/exo/worker/engines/mlx/models/qwen3/sharding.py:58— src/exo/worker/engines/mlx/models/qwen3/sharding.py:58-67 | src/exo/worker/engines/mlx/models/qwen3/sharding.py:89-98 — 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 `src/exo/worker/engines/mlx/models/qwen3/sharding.py:58` 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) src/exo/worker/engines/mlx/models/glm/glm5_next.py:303— src/exo/worker/engines/mlx/models/glm/glm5_next.py:303-312 | src/exo/worker/engines/mlx/models/nemotron_h/model.py:43-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2 locations) dashboard/src/lib/components/TopologyGraph.svelte:1077— dashboard/src/lib/components/TopologyGraph.svelte:1077 · dashboard/src/lib/components/TopologyGraph.svelte:1110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) dashboard/src/lib/components/TopologyGraph.svelte:1163— dashboard/src/lib/components/TopologyGraph.svelte:1163 · dashboard/src/lib/components/TopologyGraph.svelte:1181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:3026— dashboard/src/lib/stores/app.svelte.ts:3026 · dashboard/src/lib/stores/app.svelte.ts:3302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:3128— dashboard/src/lib/stores/app.svelte.ts:3128 · dashboard/src/lib/stores/app.svelte.ts:3415 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Repeated repair: src/exo/main.py src/exo/main.py:332— src/exo/main.py changed 17 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is Node._elect_loop at line 332), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(master): apply its own events as it decides on them; a launch that doesn't fit is refused (#2584)”; “fix: a quitting node announces that it is leaving (#2582)”; “fix: keep downloads running when a new master is elected (#2559)”; “fix(api): print the ready banner once the API serves, exit cleanly when its port is taken (#2415)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/main.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/exo/download/coordinator.py src/exo/download/coordinator.py:138— src/exo/download/coordinator.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is DownloadCoordinator._command_processor at line 138), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: a quitting node announces that it is leaving (#2582)”; “fix(download): validate model ids used as folder names (#2349)”; “fix(download): stop re-announcing ~120 unchanged download statuses every minute (#2321)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/download/coordinator.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/exo/shared/models/model_cards.py src/exo/shared/models/model_cards.py:327— src/exo/shared/models/model_cards.py changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is ConfigData.defer_to_text_config at line 327), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: never list a partly read model card catalog (#2574)”; “Nemotron-H: fix tensor and pipeline parallelism; add Nemotron 3.5 Lightning, Nemotron 3 Ultra and the Nemotron 3.5 Super-VL text path (#2515)”; “fix(worker): custom model cards survive a cluster restart (#2336)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 15:00:55 -07:00' --until='2026-11-06 15:00:55 -07:00' --full-history --no-merges -- src/exo/shared/models/model_cards.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TooManyMethods: AppStore dashboard/src/lib/stores/app.svelte.ts:620— TooManyMethods — 103 methods. The bar is 30 methods; this is 73 over it, 3.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: API REDACTED:413— TooManyMethods — 93 methods. The bar is 30 methods; this is 63 over it, 3.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: Cluster src/exo/testkit/cluster.py:432— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×3
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) src/exo/worker/engines/image/pipeline/block_wrapper.py:144— src/exo/worker/engines/image/pipeline/block_wrapper.py:144-157 | src/exo/worker/engines/image/pipeline/block_wrapper.py: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) app/EXO/EXO/Models/ClusterState.swift:90— app/EXO/EXO/Models/ClusterState.swift:90-104 | app/EXO/EXO/Models/ClusterState.swift:127-138 — 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) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:249— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:249-265 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:570-581 — 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.
Duplicated block (16 lines × 2) src/exo/api/adapters/claude.py:280— src/exo/api/adapters/claude.py:280-295 | src/exo/api/adapters/responses.py:417-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 `src/exo/api/adapters/claude.py:280` 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 (16 lines × 2) src/exo/worker/engines/image/pipeline/runner.py:925— src/exo/worker/engines/image/pipeline/runner.py:925-940 | src/exo/worker/engines/image/pipeline/runner.py:1263-1278 — 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 `src/exo/worker/engines/image/pipeline/runner.py:925` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:791— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:791-806 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:1027-1042 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:791` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/exo/worker/engines/image/models/qwen/adapter.py:116— src/exo/worker/engines/image/models/qwen/adapter.py:116-130 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:138-152 — before extracting anything, compare `src/exo/worker/engines/image/models/qwen/adapter.py` and `src/exo/worker/engines/image/models/qwen/edit_adapter.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:313— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:313-327 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:663-677 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) src/exo/worker/runner/llm_inference/batch_generator.py:170— src/exo/worker/runner/llm_inference/batch_generator.py:170-184 | src/exo/worker/runner/llm_inference/batch_generator.py:447-461 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) src/exo/worker/engines/mlx/models/glm/sharding.py:122— src/exo/worker/engines/mlx/models/glm/sharding.py:122-135 | src/exo/worker/engines/mlx/models/qwen3/sharding.py:126-139 — 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 `src/exo/worker/engines/mlx/models/glm/sharding.py:122` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/exo/worker/engines/mlx/models/qwen3/sharding.py:125` calls `all_to_sharded_linear_in_place`, `ShardedMoE` and `src/exo/worker/engines/mlx/models/glm/sharding.py:122` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (14 lines × 2) src/exo/worker/engines/image/models/qwen/adapter.py:143— src/exo/worker/engines/image/models/qwen/adapter.py:143-156 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:163-176 — before extracting anything, compare `src/exo/worker/engines/image/models/qwen/adapter.py` and `src/exo/worker/engines/image/models/qwen/edit_adapter.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) REDACTED:265— REDACTED:265-278 | app/EXO/EXO/Services/NetworkStatusService.swift:182-195 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2824— src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2824-2828 | src/exo/worker/engines/mlx/models/deepseek_v41/model.py:1606-1611 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2133— src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2133-2137 | src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2138-2142 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) REDACTED:298— REDACTED:298-302 | bench/prefill_decode_bench.py:257-261 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:297` calls `get` and `bench/prefill_decode_bench.py:255` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2 locations) dashboard/src/lib/components/ChatSidebar.svelte:197— dashboard/src/lib/components/ChatSidebar.svelte:197 · dashboard/src/lib/stores/app.svelte.ts:1195 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (15 lines × 2 locations) dashboard/src/lib/components/MarkdownContent.svelte:174— dashboard/src/lib/components/MarkdownContent.svelte:174 · dashboard/src/lib/components/MarkdownContent.svelte:191 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2 locations) dashboard/src/lib/components/ModelCard.svelte:413— dashboard/src/lib/components/ModelCard.svelte:413 · dashboard/src/lib/components/TopologyGraph.svelte:457 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (11 lines × 2 locations) dashboard/src/lib/components/TopologyGraph.svelte:988— dashboard/src/lib/components/TopologyGraph.svelte:988 · dashboard/src/lib/components/TopologyGraph.svelte:1001 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:2223— dashboard/src/lib/stores/app.svelte.ts:2223 · dashboard/src/lib/stores/app.svelte.ts:2821 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (11 lines × 2 locations) dashboard/src/routes/+page.svelte:3899— dashboard/src/routes/+page.svelte:3899 · dashboard/src/routes/+page.svelte:4083 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×2
Heading level jumps from h1 to h3 dashboard/src/routes/+page.svelte:6292— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h1 to h3 dashboard/src/routes/downloads/+page.svelte:868— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
networking::swarm::drive_membership (cognitive 36) rust/networking/src/swarm.rs:212— networking::swarm::drive_membership has cognitive complexity 36 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 4 (11 pts), loops 3 (5 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
networking::swarm::on_message (cognitive 21) rust/networking/src/swarm.rs:406— networking::swarm::on_message has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 4 (7 pts) (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
encoding.sort_tool_results_by_call_order (cognitive 30) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:567— encoding.sort_tool_results_by_call_order has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
encoding.sort_tool_results_by_call_order (cognitive 30) src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:281— encoding.sort_tool_results_by_call_order has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 3 (8 pts), boolean chains 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
encoding.parse_tool_calls (cognitive 20) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:745— encoding.parse_tool_calls has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
encoding.parse_tool_calls (cognitive 20) src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:982— encoding.parse_tool_calls has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) src/exo/worker/runner/llm_inference/batch_generator.py:264— src/exo/worker/runner/llm_inference/batch_generator.py:264-272 | src/exo/worker/runner/llm_inference/batch_generator.py:593-601 — 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) src/exo/api/serving_client.py:145— src/exo/api/serving_client.py:145-154 | src/exo/worker/serving.py:197-205 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×2
Edited copies of one member (3 members, 4+ corresponding lines) src/exo/worker/engines/mlx/models/glm/glm5_next.py:750— src/exo/worker/engines/mlx/models/glm/glm5_next.py:750-754 | src/exo/worker/engines/mlx/models/hy_v3/model.py:322-325 | src/exo/worker/engines/mlx/models/inkling/model.py:637-642 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) src/exo/worker/engines/mlx/models/glm/glm5_next.py:782— src/exo/worker/engines/mlx/models/glm/glm5_next.py:782-785 | src/exo/worker/engines/mlx/models/hy_v3/model.py:362-365 | src/exo/worker/engines/mlx/models/qwen3/qwen4_exp.py:1059-1062 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (23 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:222— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:222-244 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:182-204 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (23 lines × 2) REDACTED:454— REDACTED:454-476 | bench/prefill_decode_bench.py:411-433 — 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 `REDACTED:454` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–18 lines × 2) src/exo/utils/info_gatherer/info_gatherer.py:48— src/exo/utils/info_gatherer/info_gatherer.py:48-63 | src/exo/utils/info_gatherer/info_gatherer.py:81-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16–18 lines × 2) src/exo/worker/engines/image/models/flux/wrappers.py:122— src/exo/worker/engines/image/models/flux/wrappers.py:122-137 | src/exo/worker/engines/image/models/flux/wrappers.py:231-248 — 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 `src/exo/worker/engines/image/models/flux/wrappers.py:231` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15–16 lines × 2) REDACTED:1788— REDACTED:1788-1802 | REDACTED:1843-1858 — 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 `REDACTED:1788` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 2) src/exo/worker/runner/llm_inference/batch_generator.py:277— src/exo/worker/runner/llm_inference/batch_generator.py:277-292 | src/exo/worker/runner/llm_inference/batch_generator.py:488-502 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/exo/api/adapters/ollama.py:220— src/exo/api/adapters/ollama.py:220-232 | src/exo/api/adapters/ollama.py:402-414 — 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 `src/exo/api/adapters/ollama.py:220` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 2) src/exo/worker/engines/image/models/qwen/adapter.py:268— src/exo/worker/engines/image/models/qwen/adapter.py:268-280 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:361-373 — before extracting anything, compare `src/exo/worker/engines/image/models/qwen/adapter.py` and `src/exo/worker/engines/image/models/qwen/edit_adapter.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (12 lines × 2) src/exo/worker/engines/image/models/flux/kontext_adapter.py:212— src/exo/worker/engines/image/models/flux/kontext_adapter.py:212-223 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:436-447 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) src/exo/worker/engines/mlx/builder.py:114— src/exo/worker/engines/mlx/builder.py:114-125 | src/exo/worker/engines/mlx/builder.py:129-140 — 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 `src/exo/worker/engines/mlx/builder.py:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/prompt.py:59— src/exo/worker/engines/mlx/models/deepseek_v4/prompt.py:59-67 | src/exo/worker/engines/mlx/models/deepseek_v41/prompt.py:50-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) REDACTED:1247— REDACTED:1247-1255 | REDACTED:86-94 — 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 `REDACTED:1247` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:95` calls `write` and `REDACTED:1256` 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) src/exo/worker/engines/mlx/models/glm/sharding.py:223— src/exo/worker/engines/mlx/models/glm/sharding.py:223-230 | src/exo/worker/engines/mlx/models/hy_v3/sharding.py:50-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (8 lines × 2) REDACTED:925— REDACTED:925-932 | bench/prefill_decode_bench.py:773-780 — 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 `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.
Low cohesion: API (LCOM4 5) REDACTED:413— API's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DownloadNode (LCOM4 4) src/exo/download/tests/harness.py:137— DownloadNode's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (19 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:1972— dashboard/src/lib/stores/app.svelte.ts:1972 · dashboard/src/lib/stores/app.svelte.ts:2765 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:3596— dashboard/src/lib/stores/app.svelte.ts:3596 · dashboard/src/lib/stores/app.svelte.ts:3621 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) dashboard/src/lib/components/ChatAttachments.svelte:18— dashboard/src/lib/components/ChatAttachments.svelte:18 · dashboard/src/lib/components/ChatMessages.svelte:140 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) dashboard/src/routes/+page.svelte:597— dashboard/src/routes/+page.svelte:597 · dashboard/src/routes/+page.svelte:633 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 3 locations) dashboard/src/lib/components/ChatMessages.svelte:115— dashboard/src/lib/components/ChatMessages.svelte:115 · dashboard/src/lib/components/ChatMessages.svelte:171 · dashboard/src/lib/components/ModelPickerModal.svelte:676 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (10 lines × 3 locations) dashboard/src/routes/downloads/+page.svelte:105— dashboard/src/routes/downloads/+page.svelte:105 · dashboard/src/routes/downloads/+page.svelte:127 · dashboard/src/routes/traces/+page.svelte:60 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (10 lines × 2 locations) dashboard/src/lib/components/TopologyGraph.svelte:894— dashboard/src/lib/components/TopologyGraph.svelte:894 · dashboard/src/lib/components/TopologyGraph.svelte:908 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2 locations) dashboard/src/routes/+page.svelte:3323— dashboard/src/routes/+page.svelte:3323 · dashboard/src/routes/downloads/+page.svelte:116 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Complex function estimateMemoryGB (cyclomatic 42, cognitive 32) dashboard/src/lib/components/ModelCard.svelte:67— estimateMemoryGB has cyclomatic complexity 42 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function estimateMemoryGB (cyclomatic 42, cognitive 32) dashboard/src/routes/+page.svelte:1363— estimateMemoryGB has cyclomatic complexity 42 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Dead file (~44 LoC) dashboard/src/lib/components/HuggingFaceResultItem.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ModelPickerModal.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~44 LoC) dashboard/src/lib/utils/model_family.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~38 LoC) dashboard/src/lib/components/ImageLightbox.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/ChatMessages.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~38 LoC) dashboard/src/lib/components/PrefillProgressBar.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/ChatMessages.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~32 LoC) dashboard/src/lib/components/IntegrationCard.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~32 LoC) dashboard/src/lib/components/ToastContainer.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement dashboard/src/app.css:284— `input:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AppStore.sendMessage (cyclomatic 74) dashboard/src/lib/stores/app.svelte.ts:2573— AppStore.sendMessage has cyclomatic complexity 74 (threshold 15). Of this number, 31 points are the body's own statements and 43 belong to 6 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generate.mlx_generate (cyclomatic 50) src/exo/worker/engines/mlx/generator/generate.py:535— generate.mlx_generate has cyclomatic complexity 50 (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.
responses.responses_request_to_text_generation (cyclomatic 49) src/exo/api/adapters/responses.py:137— responses.responses_request_to_text_generation has cyclomatic complexity 49 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
encoding.render_message (cyclomatic 44) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:283— encoding.render_message has cyclomatic complexity 44 (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.
placement.place_instance (cyclomatic 43) src/exo/master/placement.py:298— placement.place_instance has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
encoding.render_message (cyclomatic 43) src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:648— encoding.render_message has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
tool_parsers._coerce_tool_arg_with_schema (cyclomatic 39) src/exo/worker/runner/llm_inference/tool_parsers.py:49— tool_parsers._coerce_tool_arg_with_schema has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppStore.generateImage (cyclomatic 38) dashboard/src/lib/stores/app.svelte.ts:3025— AppStore.generateImage has cyclomatic complexity 38 (threshold 15). Of this number, 27 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
harness.run_planning_phase (cyclomatic 37) tools/src/exo_tools/harness.py:296— harness.run_planning_phase has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DeepseekV4Cache.accumulate_windows (cyclomatic 36) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1096— DeepseekV4Cache.accumulate_windows has cyclomatic complexity 36 (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.
Master._command_processor (cyclomatic 35) src/exo/master/main.py:214— Master._command_processor has cyclomatic complexity 35 (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.
AppStore.regenerateFromToken (cyclomatic 34) dashboard/src/lib/stores/app.svelte.ts:1918— AppStore.regenerateFromToken has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 12 of the 34 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 2041, 1968, 2125, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
claude.claude_request_to_text_generation (cyclomatic 33) src/exo/api/adapters/claude.py:112— claude.claude_request_to_text_generation has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppStore.editImage (cyclomatic 33) dashboard/src/lib/stores/app.svelte.ts:3297— AppStore.editImage has cyclomatic complexity 33 (threshold 15). Of this number, 29 points are the body's own statements and 4 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.
ollama.ollama_request_to_text_generation (cyclomatic 32) src/exo/api/adapters/ollama.py:84— ollama.ollama_request_to_text_generation has cyclomatic complexity 32 (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.
ExoBatchGenerator.submit (cyclomatic 31) src/exo/worker/engines/mlx/generator/batch_generate.py:127— ExoBatchGenerator.submit has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
parser.parse_inkling (cyclomatic 30) src/exo/worker/engines/mlx/models/inkling/parser.py:71— parser.parse_inkling has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
V4Attention.__call__ (cyclomatic 29) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2290— V4Attention.__call__ has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
app.svelte.transformTopology (cyclomatic 29) dashboard/src/lib/stores/app.svelte.ts:475— app.svelte.transformTopology has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Model.sanitize (cyclomatic 27) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2863— Model.sanitize has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
chat_completions.chat_request_to_text_generation (cyclomatic 25) src/exo/api/adapters/chat_completions.py:62— chat_completions.chat_request_to_text_generation has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExoBatchGenerator.step (cyclomatic 25) src/exo/worker/engines/mlx/generator/batch_generate.py:340— ExoBatchGenerator.step has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppStore.parseSSEStream (cyclomatic 24) dashboard/src/lib/stores/app.svelte.ts:2421— AppStore.parseSSEStream has cyclomatic complexity 24 (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.
_JsonContainer._step (cyclomatic 23) src/exo/worker/engines/mlx/models/llama/parser.py:248— _JsonContainer._step has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
generate.generate_image (cyclomatic 22) src/exo/worker/engines/image/generate.py:69— generate.generate_image has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Model.sanitize (cyclomatic 22) src/exo/worker/engines/mlx/models/glm/glm5_next.py:800— Model.sanitize has cyclomatic complexity 22 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
parser.parse_tool_calls (cyclomatic 22) src/exo/worker/engines/mlx/models/minimax/parser.py:87— parser.parse_tool_calls has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
utils_mlx.render_chat_template (cyclomatic 22) src/exo/worker/engines/mlx/utils_mlx.py:585— utils_mlx.render_chat_template has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VisionEncoder.encode_images (cyclomatic 22) src/exo/worker/engines/mlx/vision.py:507— VisionEncoder.encode_images has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
harness.fetch_and_filter_placements (cyclomatic 22) tools/src/exo_tools/harness.py:205— harness.fetch_and_filter_placements has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppStore.regenerateChatCompletion (cyclomatic 22) dashboard/src/lib/stores/app.svelte.ts:2148— AppStore.regenerateChatCompletion has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 2259, 2184, 2304, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DiffusionRunner._run_sync_pass (cyclomatic 21) src/exo/worker/engines/image/pipeline/runner.py:788— DiffusionRunner._run_sync_pass has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Worker.plan_step (cyclomatic 21) src/exo/worker/main.py:308— Worker.plan_step has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
claude.generate_claude_stream (cyclomatic 20) src/exo/api/adapters/claude.py:348— claude.generate_claude_stream has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
apply.apply_node_gathered_info (cyclomatic 20) src/exo/shared/apply.py:569— apply.apply_node_gathered_info has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: apply.event_apply (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
DiffusionRunner._run_single_patch_pass (cyclomatic 20) src/exo/worker/engines/image/pipeline/runner.py:1117— DiffusionRunner._run_single_patch_pass has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Model.sanitize (cyclomatic 20) src/exo/worker/engines/mlx/models/qwen3/qwen4_exp.py:1151— Model.sanitize has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RunnerSupervisor._check_runner (cyclomatic 20) src/exo/worker/runner/supervisor.py:779— RunnerSupervisor._check_runner has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
networking::swarm::drive_membership (cyclomatic 20) rust/networking/src/swarm.rs:212— networking::swarm::drive_membership has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
download_progress.totalDownload (cyclomatic 20) dashboard/src/lib/utils/download_progress.ts:51— download_progress.totalDownload has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
chat_completions.collect_chat_response (cyclomatic 19) src/exo/api/adapters/chat_completions.py:299— chat_completions.collect_chat_response 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.
RunnerSupervisor._forward_events (cyclomatic 19) src/exo/worker/runner/supervisor.py:619— RunnerSupervisor._forward_events 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.
responses.generate_responses_stream (cyclomatic 18) src/exo/api/adapters/responses.py:482— responses.generate_responses_stream has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
transfer._fetch_once (cyclomatic 18) REDACTED:494— transfer._fetch_once has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StubEngine.step (cyclomatic 18) src/exo/testkit/stub/engine.py:176— StubEngine.step has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parser.parse_dsml_stream (cyclomatic 18) src/exo/worker/engines/mlx/models/deepseek_v3/parser.py:29— parser.parse_dsml_stream has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
API._collect_image_chunks (cyclomatic 17) REDACTED:1593— API._collect_image_chunks has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
deployments.announced (cyclomatic 17) src/exo/master/deployments.py:181— deployments.announced has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EventRouter._run_ext_in (cyclomatic 17) src/exo/routing/event_router.py:160— EventRouter._run_ext_in has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Cluster.violations (cyclomatic 17) src/exo/testkit/cluster.py:1265— Cluster.violations has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Model.sanitize (cyclomatic 17) src/exo/worker/engines/mlx/models/deepseek_v41/model.py:1691— Model.sanitize has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PipelineLastLayer.__call__ (cyclomatic 17) src/exo/worker/engines/mlx/sharding/pipeline.py:100— PipelineLastLayer.__call__ has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Worker._event_applier (cyclomatic 17) src/exo/worker/main.py:210— Worker._event_applier has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Discovery::respond (cyclomatic 17) rust/networking/src/discovery.rs:189— Discovery::respond has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Membership::tick (cyclomatic 17) rust/networking/src/membership.rs:549— Membership::tick has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
claude.collect_claude_response (cyclomatic 16) src/exo/api/adapters/claude.py:266— claude.collect_claude_response has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KVPrefixCache.get_kv_cache (cyclomatic 16) src/exo/worker/engines/mlx/cache.py:274— KVPrefixCache.get_kv_cache has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ModelArgs.__post_init__ (cyclomatic 16) src/exo/worker/engines/mlx/models/glm/glm5_next.py:121— ModelArgs.__post_init__ has cyclomatic complexity 16 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
VisionEncoder._load_weights_from_model_repo (cyclomatic 16) src/exo/worker/engines/mlx/vision.py:437— VisionEncoder._load_weights_from_model_repo has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
model_output_parsers.parse_tool_calls (cyclomatic 16) src/exo/worker/runner/llm_inference/model_output_parsers.py:215— model_output_parsers.parse_tool_calls has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ThunderboltBridgeService.disableThunderboltBridgeWithSCPreferences (cyclomatic 16) app/EXO/EXO/Services/ThunderboltBridgeService.swift:68— ThunderboltBridgeService.disableThunderboltBridgeWithSCPreferences has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DiagnosticsSummary.make (cyclomatic 16) app/EXO/EXO/Views/Settings/DiagnosticsView.swift:36— DiagnosticsSummary.make has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppStore.refreshConversationModelFromInstances (cyclomatic 16) dashboard/src/lib/stores/app.svelte.ts:1281— AppStore.refreshConversationModelFromInstances has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
responses.responses_request_to_text_generation (cognitive 111) src/exo/api/adapters/responses.py:137— responses.responses_request_to_text_generation has cognitive complexity 111 (threshold 15). Drivers by points: if/else 21 (69 pts), ternaries 8 (22 pts), loops 4 (15 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 75). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AppStore.sendMessage (cognitive 105) dashboard/src/lib/stores/app.svelte.ts:2573— AppStore.sendMessage has cognitive complexity 105 (threshold 15). Drivers by points: if/else 39 (61 pts), boolean chains 27, loops 6 (15 pts), error handling 1, ternaries 1 (nesting depth added 31). Of this number, 38 points are the body's own statements and 67 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
encoding.render_message (cognitive 78) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:283— encoding.render_message has cognitive complexity 78 (threshold 15). Drivers by points: if/else 28 (53 pts), boolean chains 13, loops 2 (9 pts), ternaries 1 (3 pts) (nesting depth added 34). 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.
encoding.render_message (cognitive 77) src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:648— encoding.render_message has cognitive complexity 77 (threshold 15). Drivers by points: if/else 26 (50 pts), boolean chains 14, loops 2 (9 pts), ternaries 2 (4 pts) (nesting depth added 33). 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.
tool_parsers._coerce_tool_arg_with_schema (cognitive 77) src/exo/worker/runner/llm_inference/tool_parsers.py:49— tool_parsers._coerce_tool_arg_with_schema has cognitive complexity 77 (threshold 15). Drivers by points: if/else 30 (59 pts), error handling 4 (12 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 39). 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.
generate.mlx_generate (cognitive 72) src/exo/worker/engines/mlx/generator/generate.py:535— generate.mlx_generate has cognitive complexity 72 (threshold 15). Drivers by points: if/else 23 (37 pts), ternaries 11 (14 pts), boolean chains 13, error handling 2 (4 pts), loops 2 (4 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chat_completions.chat_request_to_text_generation (cognitive 67) src/exo/api/adapters/chat_completions.py:62— chat_completions.chat_request_to_text_generation has cognitive complexity 67 (threshold 15). Drivers by points: if/else 20 (54 pts), loops 3 (8 pts), ternaries 3, boolean chains 2 (nesting depth added 39). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DeepseekV4Cache.accumulate_windows (cognitive 67) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1096— DeepseekV4Cache.accumulate_windows has cognitive complexity 67 (threshold 15). Drivers by points: if/else 19 (33 pts), ternaries 13 (27 pts), boolean chains 5, loops 2 (nesting depth added 28). 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.
harness.run_planning_phase (cognitive 67) tools/src/exo_tools/harness.py:296— harness.run_planning_phase has cognitive complexity 67 (threshold 15). Drivers by points: if/else 16 (40 pts), boolean chains 11, loops 7 (10 pts), ternaries 2 (6 pts) (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
claude.claude_request_to_text_generation (cognitive 65) src/exo/api/adapters/claude.py:112— claude.claude_request_to_text_generation has cognitive complexity 65 (threshold 15). Drivers by points: if/else 18 (44 pts), loops 5 (14 pts), ternaries 4 (5 pts), boolean chains 2 (nesting depth added 36). 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.
AppStore.parseSSEStream (cognitive 63) dashboard/src/lib/stores/app.svelte.ts:2421— AppStore.parseSSEStream has cognitive complexity 63 (threshold 15). Drivers by points: if/else 14 (43 pts), error handling 3 (13 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 40). 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.
ollama.ollama_request_to_text_generation (cognitive 62) src/exo/api/adapters/ollama.py:84— ollama.ollama_request_to_text_generation has cognitive complexity 62 (threshold 15). Drivers by points: if/else 16 (41 pts), ternaries 9 (12 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 30). 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.
placement.place_instance (cognitive 58) src/exo/master/placement.py:298— placement.place_instance has cognitive complexity 58 (threshold 15). Drivers by points: if/else 30 (44 pts), boolean chains 7, ternaries 2 (4 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parser.parse_inkling (cognitive 58) src/exo/worker/engines/mlx/models/inkling/parser.py:71— parser.parse_inkling has cognitive complexity 58 (threshold 15). Drivers by points: if/else 18 (51 pts), boolean chains 2, match/switch 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 35). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AppStore.generateImage (cognitive 55) dashboard/src/lib/stores/app.svelte.ts:3025— AppStore.generateImage has cognitive complexity 55 (threshold 15). Drivers by points: if/else 22 (36 pts), boolean chains 14, ternaries 1 (4 pts), error handling 1 (nesting depth added 17). Of this number, 26 points are the body's own statements and 29 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
app.svelte.transformTopology (cognitive 51) dashboard/src/lib/stores/app.svelte.ts:475— app.svelte.transformTopology has cognitive complexity 51 (threshold 15). Drivers by points: if/else 8 (27 pts), loops 6 (15 pts), boolean chains 9 (nesting depth added 28). 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.
ExoBatchGenerator.step (cognitive 49) src/exo/worker/engines/mlx/generator/batch_generate.py:340— ExoBatchGenerator.step has cognitive complexity 49 (threshold 15). Drivers by points: if/else 17 (35 pts), ternaries 2 (7 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 25). 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.
parser.parse_dsml_stream (cognitive 49) src/exo/worker/engines/mlx/models/deepseek_v3/parser.py:29— parser.parse_dsml_stream has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (39 pts), loops 2 (5 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 30). 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.
Model.sanitize (cognitive 49) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2863— Model.sanitize has cognitive complexity 49 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 11 (17 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate.generate_image (cognitive 46) src/exo/worker/engines/image/generate.py:69— generate.generate_image has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (30 pts), boolean chains 7, ternaries 2 (6 pts), loops 2 (3 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
V4Attention.__call__ (cognitive 45) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2290— V4Attention.__call__ has cognitive complexity 45 (threshold 15). Drivers by points: if/else 20 (25 pts), ternaries 9 (14 pts), boolean chains 6 (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.
Model.sanitize (cognitive 45) src/exo/worker/engines/mlx/models/glm/glm5_next.py:800— Model.sanitize has cognitive complexity 45 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 7 (16 pts), boolean chains 2 (nesting depth added 26). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Worker._event_applier (cognitive 45) src/exo/worker/main.py:210— Worker._event_applier has cognitive complexity 45 (threshold 15). Drivers by points: if/else 11 (33 pts), loops 4 (11 pts), boolean chains 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppStore.regenerateFromToken (cognitive 42) dashboard/src/lib/stores/app.svelte.ts:1918— AppStore.regenerateFromToken has cognitive complexity 42 (threshold 15). Drivers by points: if/else 21 (29 pts), boolean chains 8, loops 2 (4 pts), error handling 1 (nesting depth added 10). Most of this is not in the body itself: 10 of the 42 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 2041, 1968, 2125, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
parser.parse_tool_calls (cognitive 41) src/exo/worker/engines/mlx/models/minimax/parser.py:87— parser.parse_tool_calls has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (36 pts), boolean chains 4, loops 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VisionEncoder.encode_images (cognitive 39) src/exo/worker/engines/mlx/vision.py:507— VisionEncoder.encode_images has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (22 pts), ternaries 5 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Worker.plan_step (cognitive 39) src/exo/worker/main.py:308— Worker.plan_step has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (28 pts), ternaries 1 (5 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Cluster.violations (cognitive 38) src/exo/testkit/cluster.py:1265— Cluster.violations has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 6 (14 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExoBatchGenerator.submit (cognitive 37) src/exo/worker/engines/mlx/generator/batch_generate.py:127— ExoBatchGenerator.submit has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 8, ternaries 7, error handling 2 (4 pts), loops 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
claude.generate_claude_stream (cognitive 35) src/exo/api/adapters/claude.py:348— claude.generate_claude_stream has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppStore.editImage (cognitive 34) dashboard/src/lib/stores/app.svelte.ts:3297— AppStore.editImage has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 11, error handling 1, ternaries 1 (nesting depth added 5). Of this number, 27 points are the body's own statements and 7 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.
EventRouter._run_ext_in (cognitive 33) src/exo/routing/event_router.py:160— EventRouter._run_ext_in has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (25 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VisionEncoder._load_weights_from_separate_repo (cognitive 33) src/exo/worker/engines/mlx/vision.py:380— VisionEncoder._load_weights_from_separate_repo has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (27 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VisionEncoder._load_weights_from_model_repo (cognitive 33) src/exo/worker/engines/mlx/vision.py:437— VisionEncoder._load_weights_from_model_repo has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 4 (9 pts), boolean chains 1, ternaries 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Master._command_processor (cognitive 32) src/exo/master/main.py:214— Master._command_processor has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 2 (3 pts), ternaries 1 (3 pts), error handling 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_JsonContainer._step (cognitive 32) src/exo/worker/engines/mlx/models/llama/parser.py:248— _JsonContainer._step has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (24 pts), ternaries 2 (5 pts), boolean chains 2, match/switch 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.
PipelineLastLayer.__call__ (cognitive 32) src/exo/worker/engines/mlx/sharding/pipeline.py:100— PipelineLastLayer.__call__ has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (23 pts), ternaries 3 (7 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffusionRunner._run_single_patch_pass (cognitive 31) src/exo/worker/engines/image/pipeline/runner.py:1117— DiffusionRunner._run_single_patch_pass has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (24 pts), loops 2 (4 pts), boolean chains 3 (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.
Model.sanitize (cognitive 31) src/exo/worker/engines/mlx/models/qwen3/qwen4_exp.py:1151— Model.sanitize has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (24 pts), boolean chains 4, loops 3 (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.
RunnerSupervisor._forward_events (cognitive 31) src/exo/worker/runner/supervisor.py:619— RunnerSupervisor._forward_events has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 5, loops 2, error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffusionRunner._run_sync_pass (cognitive 29) src/exo/worker/engines/image/pipeline/runner.py:788— DiffusionRunner._run_sync_pass has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (20 pts), loops 3 (6 pts), boolean chains 3 (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.
harness.fetch_and_filter_placements (cognitive 29) tools/src/exo_tools/harness.py:205— harness.fetch_and_filter_placements has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 11, 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.
API._collect_image_chunks (cognitive 28) REDACTED:1593— API._collect_image_chunks has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 3 (6 pts), boolean chains 3, loops 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
cache.trim_cache (cognitive 28) src/exo/worker/engines/mlx/cache.py:461— cache.trim_cache has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 2 (5 pts), boolean chains 2 (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.
Model.sanitize (cognitive 28) src/exo/worker/engines/mlx/models/deepseek_v41/model.py:1691— Model.sanitize has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 2, ternaries 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chat_completions.collect_chat_response (cognitive 27) src/exo/api/adapters/chat_completions.py:299— chat_completions.collect_chat_response has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 4, ternaries 3, match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
responses.generate_responses_stream (cognitive 27) src/exo/api/adapters/responses.py:482— responses.generate_responses_stream has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, loops 2 (4 pts), ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KVPrefixCache.get_kv_cache (cognitive 27) src/exo/worker/engines/mlx/cache.py:274— KVPrefixCache.get_kv_cache has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
adapter.send_mlx_kv_cache (cognitive 27) src/exo/worker/engines/mlx/disaggregated/adapter.py:93— adapter.send_mlx_kv_cache has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils_mlx.render_chat_template (cognitive 27) src/exo/worker/engines/mlx/utils_mlx.py:585— utils_mlx.render_chat_template has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 3, loops 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RunnerSupervisor._check_runner (cognitive 27) src/exo/worker/runner/supervisor.py:779— RunnerSupervisor._check_runner has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (20 pts), boolean chains 3, error handling 2 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DiagnosticsSummary.make (cognitive 27) app/EXO/EXO/Views/Settings/DiagnosticsView.swift:36— DiagnosticsSummary.make has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
download_progress.totalDownload (cognitive 27) dashboard/src/lib/utils/download_progress.ts:51— download_progress.totalDownload has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 5 (9 pts), boolean chains 5, 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.
parser.parse_gpt_oss (cognitive 26) src/exo/worker/engines/mlx/models/gpt_oss/parser.py:23— parser.parse_gpt_oss has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (23 pts), error handling 1 (2 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harness.wait_for_instance_ready (cognitive 26) tools/src/exo_tools/harness.py:83— harness.wait_for_instance_ready has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (20 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Discovery::respond (cognitive 26) rust/networking/src/discovery.rs:189— Discovery::respond has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (21 pts), match/switch 3 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
API._generate_image_stream (cognitive 25) REDACTED:1495— API._generate_image_stream has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 1 (3 pts), boolean chains 1, loops 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.
transfer._fetch_once (cognitive 25) REDACTED:494— transfer._fetch_once has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffusionRunner._async_pipeline_step (cognitive 25) src/exo/worker/engines/image/pipeline/runner.py:1023— DiffusionRunner._async_pipeline_step has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (7 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
encoding.merge_tool_messages (cognitive 25) src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:217— encoding.merge_tool_messages has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 1 (4 pts), boolean chains 3, loops 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.
model_output_parsers.parse_tool_calls (cognitive 25) src/exo/worker/runner/llm_inference/model_output_parsers.py:215— model_output_parsers.parse_tool_calls has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 5, 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.
StubEngine.step (cognitive 24) src/exo/testkit/stub/engine.py:176— StubEngine.step has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 7 (8 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Worker._poll_connection_updates (cognitive 24) src/exo/worker/main.py:547— Worker._poll_connection_updates has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 3 (5 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppStore.regenerateChatCompletion (cognitive 24) dashboard/src/lib/stores/app.svelte.ts:2148— AppStore.regenerateChatCompletion has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 5, loops 1 (2 pts), error handling 1 (nesting depth added 3). Most of this is not in the body itself: 8 of the 24 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 2259, 2184, 2304, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
claude.collect_claude_response (cognitive 23) src/exo/api/adapters/claude.py:266— claude.collect_claude_response has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 2 (4 pts), boolean chains 2, ternaries 2 (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.
Node._elect_loop (cognitive 23) src/exo/main.py:332— Node._elect_loop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InfoGatherer._monitor_macmon (cognitive 23) src/exo/utils/info_gatherer/info_gatherer.py:583— InfoGatherer._monitor_macmon has cognitive complexity 23 (threshold 15). Drivers by points: error handling 4 (8 pts), if/else 4 (7 pts), ternaries 1 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
encoding.merge_tool_messages (cognitive 23) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:497— encoding.merge_tool_messages has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_Llama3Stream.feed (cognitive 23) src/exo/worker/engines/mlx/models/llama/parser.py:377— _Llama3Stream.feed has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
API.get_placement_previews (cognitive 22) REDACTED:781— API.get_placement_previews has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (4 pts), error handling 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
transfer.plan (cognitive 22) REDACTED:209— transfer.plan has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (2 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.
Cluster._stream_chat (cognitive 22) src/exo/testkit/cluster.py:1073— Cluster._stream_chat has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Runner.handle_generation_tasks (cognitive 22) src/exo/worker/runner/runner.py:333— Runner.handle_generation_tasks has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (5 pts), match/switch 2 (5 pts), error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThunderboltBridgeDetector.getBridgeServices (cognitive 22) app/EXO/EXO/Services/ThunderboltBridgeDetector.swift:83— ThunderboltBridgeDetector.getBridgeServices has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
downloads.indexModelDownloads (cognitive 22) dashboard/src/lib/utils/downloads.ts:173— downloads.indexModelDownloads has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
chat_completions.generate_chat_stream (cognitive 21) src/exo/api/adapters/chat_completions.py:220— chat_completions.generate_chat_stream has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (13 pts), boolean chains 5, 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.
deployments.announced (cognitive 21) src/exo/master/deployments.py:181— deployments.announced has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 7, if/else 3 (6 pts), ternaries 2 (6 pts), loops 2 (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.
Master._remove_silent_nodes_and_broken_instances (cognitive 21) src/exo/master/main.py:501— Master._remove_silent_nodes_and_broken_instances has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (6 pts), ternaries 1 (3 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.
sharding.fix_pipeline_shard (cognitive 21) src/exo/worker/engines/mlx/models/nemotron_h/sharding.py:230— sharding.fix_pipeline_shard has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), ternaries 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NGramTable.__init__ (cognitive 21) src/exo/worker/engines/mlx/models/qwen3/qwen4_exp.py:455— NGramTable.__init__ has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, 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.
VisionEncoder._load_weights (cognitive 21) src/exo/worker/engines/mlx/vision.py:299— VisionEncoder._load_weights has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PowerSampler.result (cognitive 20) src/exo/utils/power_sampler.py:55— PowerSampler.result has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 4 (6 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.
Model.sanitize (cognitive 20) src/exo/worker/engines/mlx/models/inkling/model.py:758— Model.sanitize has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parser._number_step (cognitive 20) src/exo/worker/engines/mlx/models/llama/parser.py:196— parser._number_step has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BatchGenerator.step (cognitive 20) src/exo/worker/runner/llm_inference/batch_generator.py:463— BatchGenerator.step has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 3 (6 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Membership::tick (cognitive 20) rust/networking/src/membership.rs:549— Membership::tick has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 3, match/switch 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ollama.collect_ollama_chat_response (cognitive 19) src/exo/api/adapters/ollama.py:267— ollama.collect_ollama_chat_response has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), ternaries 2, 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.
transfer.retrying (cognitive 19) REDACTED:324— transfer.retrying has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (4 pts), ternaries 1 (3 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.
apply.apply_instance_deleted (cognitive 19) src/exo/shared/apply.py:382— apply.apply_instance_deleted has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2, loops 1, ternaries 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.
Cluster.close (cognitive 19) src/exo/testkit/cluster.py:527— Cluster.close has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 4, error handling 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate.prefill (cognitive 19) src/exo/worker/engines/mlx/generator/generate.py:283— generate.prefill has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 3, loops 2 (3 pts), ternaries 3, error handling 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.
parser.parse_llama3 (cognitive 19) src/exo/worker/engines/mlx/models/llama/parser.py:472— parser.parse_llama3 has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (18 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.
prompt.split_parallel_tool_calls (cognitive 19) src/exo/worker/engines/mlx/models/llama/prompt.py:34— prompt.split_parallel_tool_calls has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 4 (8 pts), boolean chains 2 (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.
QwenShardingStrategy.shard_model (cognitive 19) src/exo/worker/engines/mlx/models/qwen3/sharding.py:40— QwenShardingStrategy.shard_model has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 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.
utils_mlx.system_prompt_token_count (cognitive 19) src/exo/worker/engines/mlx/utils_mlx.py:706— utils_mlx.system_prompt_token_count has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThunderboltBridgeService.disableThunderboltBridgeWithSCPreferences (cognitive 19) app/EXO/EXO/Services/ThunderboltBridgeService.swift:68— ThunderboltBridgeService.disableThunderboltBridgeWithSCPreferences has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2, loops 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.
downloads.modelStateOnNode (cognitive 19) dashboard/src/lib/utils/downloads.ts:233— downloads.modelStateOnNode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, ternaries 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.
ollama.collect_ollama_generate_response (cognitive 18) src/exo/api/adapters/ollama.py:445— ollama.collect_ollama_generate_response has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 1 (2 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
deployments.reconcile (cognitive 18) src/exo/master/deployments.py:399— deployments.reconcile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1, 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.
DistributedImageModel.generate (cognitive 18) src/exo/worker/engines/image/distributed_model.py:104— DistributedImageModel.generate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
client.ingest_into_mlx_cache (cognitive 18) src/exo/worker/engines/mlx/disaggregated/client.py:106— client.ingest_into_mlx_cache 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.
encoding.encode_arguments_to_dsml (cognitive 18) src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:584— encoding.encode_arguments_to_dsml has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (7 pts), error handling 1 (4 pts), ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parser.parse_muse_spark (cognitive 18) src/exo/worker/engines/mlx/models/muse_spark/parser.py:170— parser.parse_muse_spark has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (6 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
model_output_parsers.apply_all_parsers (cognitive 18) src/exo/worker/runner/llm_inference/model_output_parsers.py:54— model_output_parsers.apply_all_parsers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
quantize_and_upload.main (cognitive 18) tmp/quantize_and_upload.py:226— quantize_and_upload.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppStore.refreshConversationModelFromInstances (cognitive 18) dashboard/src/lib/stores/app.svelte.ts:1281— AppStore.refreshConversationModelFromInstances has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2, loops 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.
responses.collect_responses_response (cognitive 17) src/exo/api/adapters/responses.py:401— responses.collect_responses_response has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Node.create (cognitive 17) src/exo/main.py:102— Node.create has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 4 (5 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DeepseekV4Cache.prepare (cognitive 17) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:928— DeepseekV4Cache.prepare has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, ternaries 2 (4 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.
ModelArgs.__post_init__ (cognitive 17) src/exo/worker/engines/mlx/models/glm/glm5_next.py:121— ModelArgs.__post_init__ has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, ternaries 3 (5 pts), boolean chains 3 (nesting depth added 2). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Model.sanitize (cognitive 17) src/exo/worker/engines/mlx/models/hy_v3/model.py:367— Model.sanitize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parser._json_calls (cognitive 17) src/exo/worker/engines/mlx/models/llama/parser.py:107— parser._json_calls has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), boolean chains 3, loops 2 (3 pts), ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
downloads.getShardMetadataForModel (cognitive 17) dashboard/src/lib/utils/downloads.ts:109— downloads.getShardMetadataForModel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
API._collect_text_generation_with_stats (cognitive 16) REDACTED:1199— API._collect_text_generation_with_stats has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
main.main (cognitive 16) src/exo/main.py:413— main.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), error handling 3 (5 pts), loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
deployment_store.load (cognitive 16) src/exo/shared/deployment_store.py:122— deployment_store.load has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), error handling 3 (4 pts), loops 2 (3 pts), boolean chains 2, ternaries 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.
serving.prefill_endpoint_for (cognitive 16) src/exo/shared/serving.py:179— serving.prefill_endpoint_for has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Topology.is_rdma_cycle (cognitive 16) src/exo/shared/topology.py:258— Topology.is_rdma_cycle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 3 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiffusionRunner._run_diffusion_loop (cognitive 16) src/exo/worker/engines/image/pipeline/runner.py:537— DiffusionRunner._run_diffusion_loop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 3, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DeepseekV4Cache.update_pool (cognitive 16) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1250— DeepseekV4Cache.update_pool has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Compressor.__call__ (cognitive 16) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1664— Compressor.__call__ has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
opt_batch_gen._patched_step (cognitive 16) src/exo/worker/engines/mlx/patches/opt_batch_gen.py:84— opt_batch_gen._patched_step has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, loops 4 (8 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
utils_mlx.fix_unmatched_think_end_tokens (cognitive 16) src/exo/worker/engines/mlx/utils_mlx.py:739— utils_mlx.fix_unmatched_think_end_tokens has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 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.
model_output_parsers.parse_thinking_models (cognitive 16) src/exo/worker/runner/llm_inference/model_output_parsers.py:160— model_output_parsers.parse_thinking_models has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
tool_parsers._coerce_tool_calls_to_schema (cognitive 16) src/exo/worker/runner/llm_inference/tool_parsers.py:150— tool_parsers._coerce_tool_calls_to_schema has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 1 (2 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.
run_llm.stream_chat (cognitive 16) REDACTED:9— run_llm.stream_chat has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 2 (3 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
harness.resolve_model_short_id (cognitive 16) tools/src/exo_tools/harness.py:160— harness.resolve_model_short_id has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 4 (7 pts), loops 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExoProcessController.launch (cognitive 16) app/EXO/EXO/ExoProcessController.swift:207— ExoProcessController.launch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (2 pts), error handling 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.
app.svelte.transformNetworkInterface (cognitive 16) dashboard/src/lib/stores/app.svelte.ts:441— app.svelte.transformNetworkInterface has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassTooLong: AppStore dashboard/src/lib/stores/app.svelte.ts:620— ClassTooLong — 1950 significant lines (blank, comment-only and punctuation-only lines excluded), 103 methods. The bar is 400 significant lines; this is 1550 over it, 4.88× 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.
Change-coupling hub: utils_mlx.py → chat_completions.py, claude.py, responses.py src/exo/worker/engines/mlx/utils_mlx.py— `src/exo/worker/engines/mlx/utils_mlx.py` changes together with 3 other files — `src/exo/api/adapters/chat_completions.py`, `src/exo/api/adapters/claude.py`, `src/exo/api/adapters/responses.py` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Near-duplicate member pair (127 shared lines) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:290— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:290-489 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:655-830 — These two members are variants of one another: 127 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) src/exo/worker/runner/llm_inference/batch_generator.py:311— src/exo/worker/runner/llm_inference/batch_generator.py:311-358 | src/exo/worker/runner/llm_inference/batch_generator.py:604-645 — 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· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) src/exo/worker/engines/mlx/models/glm/sharding.py:97— src/exo/worker/engines/mlx/models/glm/sharding.py:97-135 | src/exo/worker/engines/mlx/models/gpt_oss/sharding.py:18-51 | src/exo/worker/engines/mlx/models/llama/sharding.py:17-36 | src/exo/worker/engines/mlx/models/minimax/sharding.py:108-139 | src/exo/worker/engines/mlx/models/step/sharding.py:20-55 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (149 corresponding lines) · ×1
Edited copy of a member (149 corresponding lines) src/exo/worker/engines/image/pipeline/runner.py:802— src/exo/worker/engines/image/pipeline/runner.py:802-950 | src/exo/worker/engines/image/pipeline/runner.py:1127-1285 — These two members are one piece of code written twice and then edited apart: 149 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (55 corresponding lines) · ×1
Edited copy of a member (55 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py:20— src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py:20-78 | src/exo/worker/engines/mlx/models/glm/sharding.py:35-89 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (69 corresponding lines) · ×1
Edited copy of a member (69 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:748— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:748-817 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:985-1053 — These two members are one piece of code written twice and then edited apart: 69 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) src/exo/api/adapters/ollama.py:190— src/exo/api/adapters/ollama.py:190-264 | src/exo/api/adapters/ollama.py:378-442 — These two members are one piece of code written twice and then edited apart: 65 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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, 36+ corresponding lines) · ×1
Edited copies of one member (3 members, 36+ corresponding lines) src/exo/worker/engines/mlx/models/flint/sharding.py:22— src/exo/worker/engines/mlx/models/flint/sharding.py:22-58 | src/exo/worker/engines/mlx/models/inkling/sharding.py:36-71 | src/exo/worker/engines/mlx/models/laguna/sharding.py:22-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 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 (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) src/exo/api/adapters/ollama.py:273— src/exo/api/adapters/ollama.py:273-329 | src/exo/api/adapters/ollama.py:451-491 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport 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 (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) src/exo/worker/engines/image/models/qwen/adapter.py:79— src/exo/worker/engines/image/models/qwen/adapter.py:79-138 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:99-158 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:498— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:498-564 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:218-278 — These two members are one piece of code written twice and then edited apart: 61 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) src/exo/worker/engines/mlx/models/hy_v3/model.py:131— src/exo/worker/engines/mlx/models/hy_v3/model.py:131-145 | src/exo/worker/engines/mlx/models/qwen3/qwen4_exp.py:820-835 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/prompt.py:48— src/exo/worker/engines/mlx/models/deepseek_v4/prompt.py:48-73 | src/exo/worker/engines/mlx/models/deepseek_v41/prompt.py:40-70 — 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 copy of a member (25 corresponding lines) · ×1
Edited copy of a member (25 corresponding lines) src/exo/worker/engines/mlx/sharding/pipeline.py:318— src/exo/worker/engines/mlx/sharding/pipeline.py:318-342 | src/exo/worker/engines/mlx/sharding/tensor.py:12-37 — 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 (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:626— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:626-684 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:867-896 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) src/exo/worker/engines/image/pipeline/block_wrapper.py:167— src/exo/worker/engines/image/pipeline/block_wrapper.py:167-189 | src/exo/worker/engines/image/pipeline/block_wrapper.py:266-281 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) REDACTED:120— REDACTED:120-140 | REDACTED:161-183 — 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 (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) app/EXO/EXO/Views/BugReportWindowController.swift:213— app/EXO/EXO/Views/BugReportWindowController.swift:213-236 | app/EXO/EXO/Views/BugReportWindowController.swift:238-256 — 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 copies of one member (5 members, 30+ corresponding lines) · ×1
Edited copies of one member (5 members, 30+ corresponding lines) REDACTED:1278— REDACTED:1278-1307 | REDACTED:1877-1910 | REDACTED:1915-1947 | REDACTED:1956-1987 | REDACTED:1992-2023 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 30 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 6+ corresponding lines) · ×1
Edited copies of one member (4 members, 6+ corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1599— src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1599-1606 | src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1609-1614 | src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1782-1803 | src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1808-1816 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:222— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:222-245 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:182-209 — 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 (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) rust/exo_rs/src/networking.rs:404— rust/exo_rs/src/networking.rs:404-422 | rust/exo_rs/src/networking.rs:427-443 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 71+ corresponding lines) · ×1
Edited copies of one member (3 members, 71+ corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:253— src/exo/worker/engines/mlx/models/deepseek_v4/model.py:253-347 | src/exo/worker/engines/mlx/models/deepseek_v4/model.py:400-521 | src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2498-2568 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 71 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 (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2681— src/exo/worker/engines/mlx/models/deepseek_v4/model.py:2681-2685 | src/exo/worker/engines/mlx/models/inkling/model.py:506-510 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×1
Edited copies of one member (3 members, 6+ corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/sharding.py:24— src/exo/worker/engines/mlx/models/deepseek_v4/sharding.py:24-29 | src/exo/worker/engines/mlx/models/gemma/sharding.py:22-27 | src/exo/worker/engines/mlx/sharding/blocks.py:49-54 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) src/exo/api/serving_client.py:97— src/exo/api/serving_client.py:97-106 | src/exo/worker/serving.py:150-161 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1417— src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1417-1467 | src/exo/worker/engines/mlx/models/deepseek_v41/model.py:267-303 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) src/exo/worker/engines/image/models/qwen/adapter.py:254— src/exo/worker/engines/image/models/qwen/adapter.py:254-257 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:349-352 — 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.
Duplicated block (59–72 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:821— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:821-892 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:1057-1115 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 (66 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:408— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:408-473 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:752-817 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:408` 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 (46–48 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:361— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:361-406 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:702-749 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:361` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:359` calls `format` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:702` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (35–41 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:570— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:570-610 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:284-318 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (35–37 lines × 2) src/exo/worker/engines/image/models/qwen/adapter.py:79— src/exo/worker/engines/image/models/qwen/adapter.py:79-113 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:99-135 — before extracting anything, compare `src/exo/worker/engines/image/models/qwen/adapter.py` and `src/exo/worker/engines/image/models/qwen/edit_adapter.py` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 90 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (31–34 lines × 2) src/exo/api/adapters/responses.py:653— src/exo/api/adapters/responses.py:653-686 | src/exo/api/adapters/responses.py:726-756 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (31 lines × 2) src/exo/worker/runner/llm_inference/batch_generator.py:311— src/exo/worker/runner/llm_inference/batch_generator.py:311-341 | src/exo/worker/runner/llm_inference/batch_generator.py:604-634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (28 lines × 2) REDACTED:86— REDACTED:86-113 | REDACTED:24-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (27–28 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:657— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:657-684 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:870-896 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (24–27 lines × 2) src/exo/api/adapters/ollama.py:281— src/exo/api/adapters/ollama.py:281-307 | src/exo/api/adapters/ollama.py:454-477 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/exo/api/adapters/ollama.py:308` calls `extend`, `_build_tool_calls` and `src/exo/api/adapters/ollama.py:478` 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 (25–27 lines × 2) src/exo/worker/engines/image/pipeline/runner.py:861— src/exo/worker/engines/image/pipeline/runner.py:861-887 | src/exo/worker/engines/image/pipeline/runner.py:1192-1216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/exo/worker/engines/image/pipeline/runner.py:861` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23–25 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py:24— src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py:24-48 | src/exo/worker/engines/mlx/models/glm/sharding.py:39-61 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/exo/worker/engines/mlx/models/glm/sharding.py:38` calls `cast` and `src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py:23` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24 lines × 2) src/exo/api/adapters/responses.py:688— src/exo/api/adapters/responses.py:688-711 | src/exo/api/adapters/responses.py:757-780 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18–24 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:688— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:688-711 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:839-856 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (22–23 lines × 2) src/exo/worker/engines/image/models/flux/adapter.py:131— src/exo/worker/engines/image/models/flux/adapter.py:131-153 | src/exo/worker/engines/image/models/flux/kontext_adapter.py:171-192 — before extracting anything, compare `src/exo/worker/engines/image/models/flux/adapter.py` and `src/exo/worker/engines/image/models/flux/kontext_adapter.py` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (21–23 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py:52— src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py:52-74 | src/exo/worker/engines/mlx/models/glm/sharding.py:64-84 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/exo/worker/engines/mlx/models/glm/sharding.py:85` calls `clear_cache` and `src/exo/worker/engines/mlx/models/deepseek_v3/sharding.py:76` 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 (19–22 lines × 2) src/exo/worker/engines/mlx/models/flint/sharding.py:40— src/exo/worker/engines/mlx/models/flint/sharding.py:40-58 | src/exo/worker/engines/mlx/models/laguna/sharding.py:41-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (21 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:722— src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:722-742 | src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py:461-481 — `src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py` and `src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 364 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19–20 lines × 2) src/exo/worker/engines/mlx/generator/batch_generate.py:226— src/exo/worker/engines/mlx/generator/batch_generate.py:226-245 | src/exo/worker/engines/mlx/generator/generate.py:655-673 — 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 `src/exo/worker/engines/mlx/generator/batch_generate.py:226` 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 (18 lines × 2) src/exo/worker/engines/mlx/sharding/pipeline.py:318— src/exo/worker/engines/mlx/sharding/pipeline.py:318-335 | src/exo/worker/engines/mlx/sharding/tensor.py:13-30 — 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 (12–16 lines × 2) src/exo/worker/engines/image/models/flux/kontext_adapter.py:205— src/exo/worker/engines/image/models/flux/kontext_adapter.py:205-220 | src/exo/worker/engines/image/models/qwen/edit_adapter.py:414-425 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–13 lines × 2) src/exo/worker/engines/image/pipeline/block_wrapper.py:175— src/exo/worker/engines/image/pipeline/block_wrapper.py:175-187 | src/exo/worker/engines/image/pipeline/block_wrapper.py:269-279 — 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 `src/exo/worker/engines/image/pipeline/block_wrapper.py:175` 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 `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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6–12 lines × 3) src/exo/worker/engines/mlx/models/gpt_oss/sharding.py:24— src/exo/worker/engines/mlx/models/gpt_oss/sharding.py:24-29 | src/exo/worker/engines/mlx/models/minimax/sharding.py:114-119 | src/exo/worker/engines/mlx/models/qwen3/sharding.py:91-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/exo/worker/engines/mlx/models/qwen3/sharding.py:91` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–12 lines × 2) src/exo/api/adapters/chat_completions.py:151— src/exo/api/adapters/chat_completions.py:151-162 | src/exo/api/adapters/claude.py:245-254 — 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 `src/exo/api/adapters/chat_completions.py:151` 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 (11–12 lines × 2) src/exo/worker/engines/image/models/flux/adapter.py:160— src/exo/worker/engines/image/models/flux/adapter.py:160-170 | src/exo/worker/engines/image/models/flux/kontext_adapter.py:270-281 — before extracting anything, compare `src/exo/worker/engines/image/models/flux/adapter.py` and `src/exo/worker/engines/image/models/flux/kontext_adapter.py` as WHOLE FILES: 82% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–11 lines × 4) src/exo/worker/engines/mlx/models/flint/sharding.py:24— src/exo/worker/engines/mlx/models/flint/sharding.py:24-31 | src/exo/worker/engines/mlx/models/hy_v3/sharding.py:23-30 | src/exo/worker/engines/mlx/models/inkling/sharding.py:38-45 | src/exo/worker/engines/mlx/models/laguna/sharding.py:23-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/exo/worker/engines/mlx/models/flint/sharding.py:23` calls `rank` and `src/exo/worker/engines/mlx/models/hy_v3/sharding.py:22` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–9 lines × 2) src/exo/worker/engines/image/pipeline/block_wrapper.py:147— src/exo/worker/engines/image/pipeline/block_wrapper.py:147-155 | src/exo/worker/engines/image/pipeline/block_wrapper.py:249-256 — 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 `src/exo/worker/engines/image/pipeline/block_wrapper.py: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 `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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 3) src/exo/worker/engines/mlx/models/flint/sharding.py:28— src/exo/worker/engines/mlx/models/flint/sharding.py:28-34 | src/exo/worker/engines/mlx/models/hy_v3/sharding.py:27-33 | src/exo/worker/engines/mlx/models/qwen3/sharding.py:255-261 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/exo/worker/engines/mlx/models/qwen3/sharding.py:253` calls `shard_qwen3_5_gated_delta_net` and `src/exo/worker/engines/mlx/models/flint/sharding.py: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.
Duplicated block (7 lines × 2) src/exo/api/adapters/ollama.py:168— src/exo/api/adapters/ollama.py:168-174 | src/exo/api/adapters/ollama.py:357-363 — 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 first that the copies are not typed on the same thing: the declarations holding them bind `request` to `OllamaChatRequest` in one and `OllamaGenerateRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 5) src/exo/worker/engines/mlx/models/glm/sharding.py:98— src/exo/worker/engines/mlx/models/glm/sharding.py:98-102 | src/exo/worker/engines/mlx/models/gpt_oss/sharding.py:19-23 | src/exo/worker/engines/mlx/models/llama/sharding.py:18-22 | src/exo/worker/engines/mlx/models/minimax/sharding.py:109-113 | src/exo/worker/engines/mlx/models/step/sharding.py:21-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times.
Duplicated block (6 lines × 2) src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1798— src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1798-1803 | src/exo/worker/engines/mlx/models/deepseek_v4/model.py:1811-1816 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (5 lines × 3) src/exo/api/types/api.py:437— src/exo/api/types/api.py:437-441 | src/exo/shared/types/worker/runner_response.py:37-41 | src/exo/shared/types/worker/runner_response.py:52-56 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 3) src/exo/worker/engines/mlx/models/glm/glm5_next.py:774— src/exo/worker/engines/mlx/models/glm/glm5_next.py:774-779 | src/exo/worker/engines/mlx/models/hy_v3/model.py:349-354 | src/exo/worker/engines/mlx/models/qwen3/qwen4_exp.py:1046-1051 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `ModelArgs` in one and `TextArgs` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (25 lines × 2) app/EXO/EXO/Services/NetworkStatusService.swift:204— app/EXO/EXO/Services/NetworkStatusService.swift:204-228 | app/EXO/EXO/Services/ThunderboltBridgeDetector.swift:169-193 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) REDACTED:263— REDACTED:263-269 | REDACTED:1332-1337 — 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.
Duplicated block (23–27 lines × 2) bench/eval_tool_calls.py:693— bench/eval_tool_calls.py:693-715 | bench/eval_tool_calls.py:795-821 — 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 `bench/eval_tool_calls.py:693` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (22 lines × 2) REDACTED:429— REDACTED:429-450 | bench/prefill_decode_bench.py:392-413 — 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 `REDACTED:429` 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 (19–21 lines × 2) bench/eval_tool_calls.py:371— bench/eval_tool_calls.py:371-389 | bench/eval_tool_calls.py:479-499 — 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 `bench/eval_tool_calls.py:479` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (12–13 lines × 2) REDACTED:521— REDACTED:521-532 | bench/prefill_decode_bench.py:487-499 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8–11 lines × 2) REDACTED:628— REDACTED:628-638 | REDACTED:1525-1532 — 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 `REDACTED:628` 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.
Off the main sequence: networking — networking: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the node:test suite in dashboard/ ran and not one test passed (throw new ERR_UNKNOWN_FILE_EXTENSION(ext, filepath);), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Outbound HTTP without resilience REDACTED:20— `requests.post(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Duplication concentrated across 2 sibling directories (9 clone groups) dashboard/src/lib/components/ModelCard.svelte:63— 9 duplicated blocks under dashboard/src/ have copies in at least two of the sibling directories lib, routes — 5 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplicated block (61 lines × 2 locations) dashboard/src/lib/components/TopologyGraph.svelte:635— dashboard/src/lib/components/TopologyGraph.svelte:635 · dashboard/src/lib/components/TopologyGraph.svelte:718 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (41 matched lines × 2 locations) · ×1
Duplicated block with local edits (41 matched lines × 2 locations) dashboard/src/routes/traces/+page.svelte:77— dashboard/src/routes/traces/+page.svelte:77 · dashboard/src/routes/traces/[taskId]/+page.svelte:79 — the two spans are one implementation copied and then locally edited — 236 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (35 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:3258— dashboard/src/lib/stores/app.svelte.ts:3258 · dashboard/src/lib/stores/app.svelte.ts:3507 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (34 lines × 2 locations) dashboard/src/lib/components/ModelCard.svelte:63— dashboard/src/lib/components/ModelCard.svelte:63 · dashboard/src/routes/+page.svelte:1359 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (32 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:1339— dashboard/src/lib/stores/app.svelte.ts:1339 · dashboard/src/lib/stores/app.svelte.ts:1426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (28 lines × 2 locations) dashboard/src/lib/components/TopologyGraph.svelte:1043— dashboard/src/lib/components/TopologyGraph.svelte:1043 · dashboard/src/lib/components/TopologyGraph.svelte:1118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:2019— dashboard/src/lib/stores/app.svelte.ts:2019 · dashboard/src/lib/stores/app.svelte.ts:2237 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 3 locations) dashboard/src/lib/stores/app.svelte.ts:2081— dashboard/src/lib/stores/app.svelte.ts:2081 · dashboard/src/lib/stores/app.svelte.ts:2286 · dashboard/src/lib/stores/app.svelte.ts:2905 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (24 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:3149— dashboard/src/lib/stores/app.svelte.ts:3149 · dashboard/src/lib/stores/app.svelte.ts:3435 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (22 lines × 2 locations) dashboard/src/routes/+page.svelte:1036— dashboard/src/routes/+page.svelte:1036 · dashboard/src/routes/+page.svelte:4281 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 3 locations) dashboard/src/lib/stores/app.svelte.ts:2660— dashboard/src/lib/stores/app.svelte.ts:2660 · dashboard/src/lib/stores/app.svelte.ts:3045 · dashboard/src/lib/stores/app.svelte.ts:3322 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (16 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:1998— dashboard/src/lib/stores/app.svelte.ts:1998 · dashboard/src/lib/stores/app.svelte.ts:2214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) dashboard/src/lib/components/ChatMessages.svelte:205— dashboard/src/lib/components/ChatMessages.svelte:205 · dashboard/src/lib/components/ChatSidebar.svelte:71 — the two spans are one implementation copied and then locally edited — 50 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (13 lines × 2 locations) dashboard/src/lib/stores/app.svelte.ts:2325— dashboard/src/lib/stores/app.svelte.ts:2325 · dashboard/src/lib/stores/app.svelte.ts:2971 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function (anonymous) (cyclomatic 65, cognitive 103) dashboard/src/lib/components/TopologyGraph.svelte:529— (anonymous) has cyclomatic complexity 65 and cognitive complexity 103; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function collectDownloadStatus (cyclomatic 50, cognitive 86) dashboard/src/routes/+page.svelte:2100— collectDownloadStatus has cyclomatic complexity 50 and cognitive complexity 86; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 42, cognitive 63) dashboard/src/routes/downloads/+page.svelte:233— (anonymous) has cyclomatic complexity 42 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 35, cognitive 58) dashboard/src/routes/+page.svelte:3493— (anonymous) has cyclomatic complexity 35 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function transformTopology (cyclomatic 33, cognitive 61) dashboard/src/lib/stores/app.svelte.ts:475— transformTopology has cyclomatic complexity 33 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function estimatePerformance (cyclomatic 32, cognitive 23) dashboard/src/routes/+page.svelte:1439— estimatePerformance has cyclomatic complexity 32 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleAutoSend (cyclomatic 31, cognitive 39) dashboard/src/routes/+page.svelte:3930— handleAutoSend has cyclomatic complexity 31 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function sendMessage (cyclomatic 31, cognitive 38) dashboard/src/lib/stores/app.svelte.ts:2573— sendMessage has cyclomatic complexity 31 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function deriveInstanceStatus (cyclomatic 29, cognitive 38) dashboard/src/routes/+page.svelte:2756— deriveInstanceStatus has cyclomatic complexity 29 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function editImage (cyclomatic 29, cognitive 30) dashboard/src/lib/stores/app.svelte.ts:3297— editImage has cyclomatic complexity 29 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateImage (cyclomatic 27, cognitive 29) dashboard/src/lib/stores/app.svelte.ts:3025— generateImage has cyclomatic complexity 27 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseSSEStream (cyclomatic 24, cognitive 63) dashboard/src/lib/stores/app.svelte.ts:2421— parseSSEStream has cyclomatic complexity 24 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 24, cognitive 40) dashboard/src/lib/stores/app.svelte.ts:2698— (anonymous) has cyclomatic complexity 24 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseDownloadProgress (cyclomatic 22, cognitive 19) dashboard/src/routes/+page.svelte:2037— parseDownloadProgress has cyclomatic complexity 22 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function totalDownload (cyclomatic 20, cognitive 26) dashboard/src/lib/utils/download_progress.ts:51— totalDownload has cyclomatic complexity 20 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fetchState (cyclomatic 19, cognitive 20) dashboard/src/lib/stores/app.svelte.ts:1577— fetchState has cyclomatic complexity 19 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function extractModelCard (cyclomatic 19, cognitive 15) dashboard/src/routes/downloads/+page.svelte:158— extractModelCard has cyclomatic complexity 19 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 17) dashboard/src/routes/+page.svelte:276— (anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 17) dashboard/src/lib/components/ModelPickerModal.svelte:407— (anonymous) has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getInstanceConnections (cyclomatic 16, cognitive 26) dashboard/src/routes/+page.svelte:3216— getInstanceConnections has cyclomatic complexity 16 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function refreshConversationModelFromInstances (cyclomatic 16, cognitive 18) dashboard/src/lib/stores/app.svelte.ts:1281— refreshConversationModelFromInstances has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 17) dashboard/src/routes/+page.svelte:3636— (anonymous) has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function indexModelDownloads (cyclomatic 15, cognitive 24) dashboard/src/lib/utils/downloads.ts:173— indexModelDownloads has cyclomatic complexity 15 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function transformNetworkInterface (cyclomatic 15, cognitive 17) dashboard/src/lib/stores/app.svelte.ts:441— transformNetworkInterface has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getConnectionInfo (cyclomatic 15, cognitive 16) dashboard/src/lib/components/ModelCard.svelte:432— getConnectionInfo has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderGraph (cyclomatic 15, cognitive 16) dashboard/src/lib/components/TopologyGraph.svelte:169— renderGraph has cyclomatic complexity 15 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 14) dashboard/src/lib/components/TopologyGraph.svelte:330— (anonymous) has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getInterfaceForIp (cyclomatic 14, cognitive 18) dashboard/src/lib/components/ModelCard.svelte:372— getInterfaceForIp has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function observe (cyclomatic 14, cognitive 18) dashboard/src/lib/utils/download_activity.ts:40— observe has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function resolveConversationInfo (cyclomatic 14, cognitive 15) dashboard/src/lib/components/ChatSidebar.svelte:223— resolveConversationInfo has cyclomatic complexity 14 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function modelStateOnNode (cyclomatic 13, cognitive 19) dashboard/src/lib/utils/downloads.ts:233— modelStateOnNode has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getArrow (cyclomatic 13, cognitive 18) dashboard/src/lib/components/TopologyGraph.svelte:452— getArrow has cyclomatic complexity 13 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 17) dashboard/src/lib/stores/app.svelte.ts:2858— (anonymous) has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 13, cognitive 15) dashboard/src/routes/+page.svelte:3051— (anonymous) has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getRunnerFailures (cyclomatic 12, cognitive 17) dashboard/src/routes/+page.svelte:2594— getRunnerFailures has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 17) dashboard/src/routes/+page.svelte:4232— (anonymous) has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 16) dashboard/src/lib/stores/app.svelte.ts:2041— (anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parseDeployments (cyclomatic 12, cognitive 16) dashboard/src/lib/utils/deployments.ts:109— parseDeployments has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· dashboard/src/routes/+page.svelte · ×1
dashboard/src/routes/+page.svelte: 7918 lines of code dashboard/src/routes/+page.svelte:1— dashboard/src/routes/+page.svelte has 7918 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/stores/app.svelte.ts · ×1
dashboard/src/lib/stores/app.svelte.ts: 3557 lines of code dashboard/src/lib/stores/app.svelte.ts:1— dashboard/src/lib/stores/app.svelte.ts has 3557 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/ModelPickerModal.svelte · ×1
dashboard/src/lib/components/ModelPickerModal.svelte: 1198 lines of code dashboard/src/lib/components/ModelPickerModal.svelte:1— dashboard/src/lib/components/ModelPickerModal.svelte has 1198 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/TopologyGraph.svelte · ×1
dashboard/src/lib/components/TopologyGraph.svelte: 1152 lines of code dashboard/src/lib/components/TopologyGraph.svelte:1— dashboard/src/lib/components/TopologyGraph.svelte has 1152 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/ModelCard.svelte · ×1
dashboard/src/lib/components/ModelCard.svelte: 1037 lines of code dashboard/src/lib/components/ModelCard.svelte:1— dashboard/src/lib/components/ModelCard.svelte has 1037 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/routes/downloads/+page.svelte · ×1
dashboard/src/routes/downloads/+page.svelte: 956 lines of code dashboard/src/routes/downloads/+page.svelte:1— dashboard/src/routes/downloads/+page.svelte has 956 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/MarkdownContent.svelte · ×1
dashboard/src/lib/components/MarkdownContent.svelte: 947 lines of code dashboard/src/lib/components/MarkdownContent.svelte:1— dashboard/src/lib/components/MarkdownContent.svelte has 947 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/ChatMessages.svelte · ×1
dashboard/src/lib/components/ChatMessages.svelte: 830 lines of code dashboard/src/lib/components/ChatMessages.svelte:1— dashboard/src/lib/components/ChatMessages.svelte has 830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/ModelPickerGroup.svelte · ×1
dashboard/src/lib/components/ModelPickerGroup.svelte: 690 lines of code dashboard/src/lib/components/ModelPickerGroup.svelte:1— dashboard/src/lib/components/ModelPickerGroup.svelte has 690 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/routes/integrations/+page.svelte · ×1
dashboard/src/routes/integrations/+page.svelte: 655 lines of code dashboard/src/routes/integrations/+page.svelte:1— dashboard/src/routes/integrations/+page.svelte has 655 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/ImageParamsPanel.svelte · ×1
dashboard/src/lib/components/ImageParamsPanel.svelte: 644 lines of code dashboard/src/lib/components/ImageParamsPanel.svelte:1— dashboard/src/lib/components/ImageParamsPanel.svelte has 644 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/ChatSidebar.svelte · ×1
dashboard/src/lib/components/ChatSidebar.svelte: 588 lines of code dashboard/src/lib/components/ChatSidebar.svelte:1— dashboard/src/lib/components/ChatSidebar.svelte has 588 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/ChatForm.svelte · ×1
dashboard/src/lib/components/ChatForm.svelte: 560 lines of code dashboard/src/lib/components/ChatForm.svelte:1— dashboard/src/lib/components/ChatForm.svelte has 560 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte · ×1
dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte: 536 lines of code dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte:1— dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte has 536 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~3951 LoC) dashboard/src/lib/stores/app.svelte.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1250 LoC) dashboard/src/lib/components/TopologyGraph.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~715 LoC) dashboard/src/lib/components/ModelPickerModal.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~533 LoC) dashboard/src/lib/components/MarkdownContent.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ChatMessages.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~483 LoC) dashboard/src/lib/components/ModelCard.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~333 LoC) dashboard/src/lib/types/files.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~264 LoC) dashboard/src/lib/components/ChatForm.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~262 LoC) dashboard/src/lib/components/ChatSidebar.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~261 LoC) dashboard/src/lib/components/ChatMessages.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~251 LoC) dashboard/src/lib/components/ChatModelSelector.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~206 LoC) dashboard/src/lib/components/PrefillDecodeDisaggregation.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~174 LoC) dashboard/src/lib/components/ImageParamsPanel.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ChatForm.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~162 LoC) dashboard/src/lib/components/ModelPickerGroup.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ModelPickerModal.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~133 LoC) dashboard/src/lib/components/TokenHeatmap.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (dashboard/src/lib/components/ChatMessages.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~115 LoC) dashboard/src/lib/components/DeviceIcon.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~102 LoC) dashboard/src/lib/stores/toast.svelte.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~97 LoC) dashboard/src/lib/stores/favorites.svelte.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~75 LoC) dashboard/src/lib/stores/recents.svelte.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~69 LoC) dashboard/src/lib/components/ModelFilterPopover.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ModelPickerModal.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~67 LoC) dashboard/src/lib/components/HeaderNav.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~55 LoC) dashboard/src/lib/utils/clipboard.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~42 LoC) dashboard/src/lib/components/FamilySidebar.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ModelPickerModal.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~35 LoC) dashboard/src/lib/components/ChatAttachments.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/ChatForm.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~16 LoC) dashboard/src/lib/components/index.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~11 LoC) dashboard/src/lib/utils/brand_colors.ts— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~7 LoC) dashboard/src/lib/components/FamilyLogos.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (dashboard/src/lib/components/FamilySidebar.svelte, dashboard/src/lib/components/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~5 LoC) dashboard/src/lib/components/ConnectionBanner.svelte— no import path from any entry point (8 application, 3 tooling, 14 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency 'devalue' — Declared in dashboard/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'mode-watcher' — Declared in dashboard/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Orphaned file src/exo/worker/engines/image/models/qwen/edit_adapter.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file tmp/quantize_and_upload.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/image/models/flux/kontext_adapter.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/image/models/qwen/adapter.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/image/models/base.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/image/pipeline/block_wrapper.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/image/models/flux/wrappers.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file tools/src/exo_tools/cluster.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/image/models/qwen/wrappers.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/shared/tracing.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/utils/disk_event_log.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/shared/types/memory.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/mlx/disaggregated/client.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file tools/src/exo_tools/client.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/mlx/patches/standard_yarn_rope.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file scripts/fetch_kv_heads.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/disaggregated/protocol.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/disaggregated/server.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file app/EXO/EXO/main.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/shared/types/thunderbolt.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/image/pipeline/kv_cache.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/exo/worker/engines/mlx/generator/remote_prefill.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:659— `add_default_bos_token and len(context) == 0` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/api/adapters/chat_completions.py:236— `chunk.error_message or "Internal server error"` appears character-identically in 3 files — src/exo/api/adapters/chat_completions.py, src/exo/api/adapters/ollama.py, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/exo/api/adapters/chat_completions.py:360— `error.error_message or "Internal server error"` appears character-identically in 3 files — src/exo/api/adapters/chat_completions.py, src/exo/api/adapters/claude.py, src/exo/api/adapters/responses.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:448— `index + 1 < len(messages) and messages[index + 1].get("role") not in [ "assistant", "latest_reminder", ]` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:422— `index - 1 >= 0 and messages[index - 1].get("task") is not None` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:334— `index == 0 and thinking_mode == "thinking"` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/shared/model_readiness.py:221— `isinstance(download, DownloadFailed) and download.shard_metadata.model_card.model_id == model_id` appears character-identically in 2 files — src/exo/shared/model_readiness.py, src/exo/worker/main.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:872— `len(text) == index and stop_token in [eos_token, None]` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:595— `len(tool_blocks) > 1 and last_tool_call_order` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v41/model.py:1705— `match is not None and int(match.group(1)) >= n_layers` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v41/model.py, src/exo/worker/engines/mlx/models/hy_v3/model.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:529— `merged and merged[-1].get("role") == "user" and "content_blocks" in merged[-1]` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:544— `merged and merged[-1].get("role") == "user" and "content_blocks" in merged[-1] and merged[-1].get("task") is None` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/image/models/qwen/adapter.py:229— `negative_prompt is None or negative_prompt == ""` appears character-identically in 2 files — src/exo/worker/engines/image/models/qwen/adapter.py, src/exo/worker/engines/image/models/qwen/edit_adapter.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:425— `not drop_thinking or index > last_user_idx` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/generator/batch_generate.py:541— `prefix_hit_length >= min_prefix_hit_length and hit_ratio >= _MIN_PREFIX_HIT_RATIO_TO_UPDATE` appears character-identically in 2 files — src/exo/worker/engines/mlx/generator/batch_generate.py, src/exo/worker/engines/mlx/generator/generate.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:584— `role == "assistant" and msg.get("tool_calls")` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:591— `role == "user" and msg.get("content_blocks")` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:703— `role in keep_roles or idx >= last_user_idx` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:883— `sp_token not in summary_content and sp_token not in reasoning_content` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:665— `thinking_mode == "thinking" and effective_drop_thinking` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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 src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py:424— `thinking_mode == "thinking" and not prev_has_task` appears character-identically in 2 files — src/exo/worker/engines/mlx/models/deepseek_v4/encoding.py, src/exo/worker/engines/mlx/models/deepseek_v41/encoding.py. 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.
Silent fallback default on parse failure src/exo/routing/wire.py:61— `_installed` returns `'none'` when `ImportError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure src/exo/routing/wire_schema.py:186— `_source_hash` returns `'unavailable'` when `(OSError, TypeError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 10 significant file(s) lose their only recent owner: app/EXO/EXO/Views/BugReportWindowController.swift, dashboard/src/lib/utils/downloads.ts, app/EXO/EXO/Models/ClusterState.swift, app/EXO/EXO/Models/StartupPreferences.swift, src/exo/api/collected_response.py, app/EXO/EXO/Models/ExoLogFile.swift, app/EXO/EXO/Models/MenuBarIconStyle.swift, REDACTED (+2 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (15 single-owned of 226 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 226 of the 387 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/exo/worker/engines/image/pipeline/runner.py, src/exo/worker/engines/image/models/__init__.py, src/exo/utils/async_process.py, rust/exo_rs/src/pidfile.rs, scripts/download_model_to_cluster.py.
No ADRs found REDACTED:32— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `REDACTED` makes this repository a deployable product (line 32).
D21 · Naming Consistency· `uploadToPresignedUrl` spells `Url` where 14 names in the project spell it `URL` · ×1
`uploadToPresignedUrl` spells `Url` where 14 names in the project spell it `URL` REDACTED:295— 14 of 15 names in project repository spell the token `URL` (14 of 15; unit: names in project repository containing `URL`). Peers: ExoProcessController.exoDirectoryURL (app/EXO/EXO/ExoProcessController.swift:37); ExoProcessController.runtimeDirectoryURL (app/EXO/EXO/ExoProcessController.swift:162); ExoProcessController.makeEnvironment(runtimeURL) (app/EXO/EXO/ExoProcessController.swift:547); ExoLogFile.rotatedURL (app/EXO/EXO/Models/ExoLogFile.swift:19); ExoPidLock.fileURL (app/EXO/EXO/Models/ExoPidLock.swift:9). Rename to `uploadToPresignedURL`. [rule N6]
D21 · Naming Consistency· `UninstallEXO` spells `EXO` where 15 names in the project spell it `Exo` · ×1
`UninstallEXO` spells `EXO` where 15 names in the project spell it `Exo` app/EXO/EXO/Views/Settings/UninstallEXO.swift:5— 15 of 16 names in project repository spell the token `Exo` (15 of 16; unit: names in project repository containing `Exo`). Peers: AppDelegate.stopExoBeforeQuitting (app/EXO/EXO/AppDelegate.swift:14); ExoProcessController.previousExoIsRunning (app/EXO/EXO/ExoProcessController.swift:168); ExoProcessController.init(previousExoIsRunning) (app/EXO/EXO/ExoProcessController.swift:173); ExoProcessController.launchWhenPreviousExoHasExited (app/EXO/EXO/ExoProcessController.swift:492); BugReportService.readExoMetadata (REDACTED:379). Rename to `UninstallExo`. [rule N6]
redundant comment dashboard/src/lib/stores/app.svelte.ts:703— 11 comments in this file only repeat the code they sit on (lines 703, 708, 1628, 2172, 2300, 2683, 2699, 2921, 3068, 3345, 3924), for example "Image generation params". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 6 project(s) overshoot their size bounds, lowering Project Cohesion to 4.6/10. The most over is `(repository root)` (50029 LoC, 900 module-visible types across 52 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 24 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: src/exo/worker/engines/image/models/qwen/edit_adapter.py, tmp/quantize_and_upload.py, src/exo/worker/engines/image/models/flux/kontext_adapter.py, src/exo/worker/engines/image/models/base.py, src/exo/worker/engines/image/pipeline/block_wrapper.py, src/exo/worker/engines/image/models/flux/wrappers.py, REDACTED, tools/src/exo_tools/cluster.py (and 16 more) (25 orphaned of 226 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 226 of the 387 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 4/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `dashboard`.
No SAST REDACTED:5— No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation dashboard/package.json:14— `dashboard/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
R7 · Dead Code· Unused export 'readApiErrorMessage' · ×1
Unused export 'readApiErrorMessage' dashboard/src/lib/utils/api_errors.ts:23— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getNodesWithModelDownloaded' · ×1
Unused export 'getNodesWithModelDownloaded' dashboard/src/lib/utils/downloads.ts:92— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getShardMetadataForModel' · ×1
Unused export 'getShardMetadataForModel' dashboard/src/lib/utils/downloads.ts:109— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'getModelDownloadStatus' · ×1
Unused export 'getModelDownloadStatus' dashboard/src/lib/utils/downloads.ts:136— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'OTHER_VERSIONS_FAILED_ASKS_BEFORE_DROPPING' · ×1
Unused export 'OTHER_VERSIONS_FAILED_ASKS_BEFORE_DROPPING' dashboard/src/lib/utils/other_versions.ts:105— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused module-local declaration 'formatLastUpdate' · ×1
Unused module-local declaration 'formatLastUpdate' dashboard/src/routes/+page.svelte:3083— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 3/19 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Interpolated log message defeats structured logging tools/src/exo_tools/cluster.py:127— `info` at line 127 is handed an f-string as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the record is filtered out. Pass the values beside a constant message instead: `logger.info("order %s moved to %s", order_id, status)` with the standard library's `logging`, which keeps the message and its arguments apart on the record, or `log.info("order moved", order_id=order_id, status=status)` with structlog.
Silent fallback default in catch app/EXO/EXO/Models/ExoLogFile.swift:61— `text` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Outdated: blake3 — `blake3` is locked at 1.8.5 but 1.8.7 is the current stable release on crates.io, and it already satisfies the `"1.8.5"` requirement declared in rust/networking/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p blake3` and commit the updated REDACTED.
Outdated: bytemuck — `bytemuck` is locked at 1.25.0 but 1.25.2 is the current stable release on crates.io, and it already satisfies the `"1.25.0"` requirement declared in rust/networking/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytemuck` and commit the updated REDACTED.
Outdated: env_logger — `env_logger` is locked at 0.11.10 but 0.11.11 is the current stable release on crates.io, and it already satisfies the `"0.11.10"` requirement declared in rust/exo_rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p env_logger` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.186 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in rust/exo_rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.30 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in rust/exo_rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: pyo3-log — `pyo3-log` is locked at 0.13.3 but 0.13.5 is the current stable release on crates.io, and it already satisfies the `"0.13.3"` requirement declared in rust/exo_rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p pyo3-log` and commit the updated REDACTED.
Outdated: rand — `rand` is locked at 0.10.1 but 0.10.3 is the current stable release on crates.io, and it already satisfies the `"0.10.1"` requirement declared in rust/exo_rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rand` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.150 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1.0.149"` requirement declared in rust/exo_rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde_json` and commit the updated REDACTED.
Outdated: socket2 — `socket2` is locked at 0.6.4 but 0.6.5 is the current stable release on crates.io, and it already satisfies the `"0.6.4"` requirement declared in rust/networking/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p socket2` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.52.3 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1.46"` requirement declared in rust/exo_rs/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
doc comments repeat the names dashboard/src/lib/stores/app.svelte.ts:1040— 1 of 15 documented parameters and 5 of 150 summaries in `exo-dashboard` only repeat the member or parameter name (e.g. "Create a new conversation" for `createConversation`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 25 file(s) — `.typings/mlx/core/__init__.pyi`, `src/exo/api/adapters/chat_completions.py`, `src/exo/api/command_acceptance.py`, `src/exo/download/coordinator.py`, `src/exo/download/hub.py`, … (+20 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
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.
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.
Run 01a1d794-a6ed-7ad5-b7b1-179ef5ce2802 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 84 · Warnings: 695 · Recommendations: 82 · Info: 11 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 01:03 UTC.
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.