Public report of unicity-aos/aos-ce, 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, 16:54 UTC · Survey ID cd_1bf42f0ce8a74762bac08cdb84889e04
unicity-aos/aos-ce
Measured 14 November 2026, 16:54 UTC, at code version 6e4e8ec
CAI scoreStrong
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 68,297 lines of product code in 32 projects, tests not counted · Estimated rebuild effort: about 0.8 person-years · Weakest lens: Performance, 70
Findings by how serious they are
0 critical298 serious33 minor
22 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, 16:54 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
45of 45 dimensions measured by tools.
314of 331 findings point to an exact file and line, so you can open each one in the code. The other 17 concern the repository as a whole, such as missing documentation.
45dimensions across 7 lenses, read from 68,297 lines of product code in 32 projects.
unicity-aos/aos-ce meets our standard for production. It scores 74 out of 100 and is rated Strong, and it has no critical findings.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step for the work it takes is recording design decisions, worth about 3 points. Removing the blocking calls comes next, worth about 4 points.
Most of the 298 serious findings are in Code Health.
The product code is 68,297 lines, about €120,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts 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.
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: 25 findings
These 25 critical or serious findings were in the previous survey, on 27 October 2026, and are gone from this one.
€40,000 to €200,000, for 663 to 2,102 hours of work, about 0.8 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
×1.1 at a score of 74. 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: 68,297 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
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
Raises the score by about 3 points · Low effort · ADR Quality
2
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
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.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
132 modules, with 105 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 92 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.
adaptive_shell.activity uses adaptive_shell.components, so a change to adaptive_shell.components can break adaptive_shell.activity, while a change to adaptive_shell.activity can't break adaptive_shell.components.
Position
Below the diagonal: adaptive_shell.activity uses a module listed above it, which is the healthy direction.
adaptive_shell.reconcile uses adaptive_shell.components, so a change to adaptive_shell.components can break adaptive_shell.reconcile, while a change to adaptive_shell.reconcile can't break adaptive_shell.components.
Position
Below the diagonal: adaptive_shell.reconcile uses a module listed above it, which is the healthy direction.
aos_users.requests uses aos_users.types, so a change to aos_users.types can break aos_users.requests, while a change to aos_users.requests can't break aos_users.types.
Position
Below the diagonal: aos_users.requests uses a module listed above it, which is the healthy direction.
capsule_surface_model.bindings uses capsule_surface_model.activity, so a change to capsule_surface_model.activity can break capsule_surface_model.bindings, while a change to capsule_surface_model.bindings can't break capsule_surface_model.activity.
Position
Below the diagonal: capsule_surface_model.bindings uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.policy uses capsule_surface_model.activity, so a change to capsule_surface_model.activity can break capsule_workspace_recipes.policy, while a change to capsule_workspace_recipes.policy can't break capsule_surface_model.activity.
Position
Below the diagonal: capsule_workspace_recipes.policy uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.policy uses capsule_surface_model.canonical, so a change to capsule_surface_model.canonical can break capsule_workspace_recipes.policy, while a change to capsule_workspace_recipes.policy can't break capsule_surface_model.canonical.
Position
Below the diagonal: capsule_workspace_recipes.policy uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.mcp uses unicity_aos_bootstrap, so a change to unicity_aos_bootstrap can break unicity_aos_bootstrap.mcp, while a change to unicity_aos_bootstrap.mcp can't break unicity_aos_bootstrap.
Position
Below the diagonal: unicity_aos_bootstrap.mcp uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.mcp.interaction uses unicity_aos_bootstrap.mcp.interaction.consent, so a change to unicity_aos_bootstrap.mcp.interaction.consent can break unicity_aos_bootstrap.mcp.interaction, while a change to unicity_aos_bootstrap.mcp.interaction can't break unicity_aos_bootstrap.mcp.interaction.consent.
Position
Below the diagonal: unicity_aos_bootstrap.mcp.interaction uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.status uses unicity_aos_bootstrap, so a change to unicity_aos_bootstrap can break unicity_aos_bootstrap.status, while a change to unicity_aos_bootstrap.status can't break unicity_aos_bootstrap.
Position
Below the diagonal: unicity_aos_bootstrap.status uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.updates uses unicity_aos_bootstrap, so a change to unicity_aos_bootstrap can break unicity_aos_bootstrap.updates, while a change to unicity_aos_bootstrap.updates can't break unicity_aos_bootstrap.
Position
Below the diagonal: unicity_aos_bootstrap.updates uses a module listed above it, which is the healthy direction.
adaptive_shell.atlas uses adaptive_shell.layout, so a change to adaptive_shell.layout can break adaptive_shell.atlas, while a change to adaptive_shell.atlas can't break adaptive_shell.layout.
Position
Below the diagonal: adaptive_shell.atlas uses a module listed above it, which is the healthy direction.
adaptive_shell.atlas uses adaptive_shell.activity, so a change to adaptive_shell.activity can break adaptive_shell.atlas, while a change to adaptive_shell.atlas can't break adaptive_shell.activity.
Position
Below the diagonal: adaptive_shell.atlas uses a module listed above it, which is the healthy direction.
capsule_surface_model.recipe uses capsule_surface_model.activity, so a change to capsule_surface_model.activity can break capsule_surface_model.recipe, while a change to capsule_surface_model.recipe can't break capsule_surface_model.activity.
Position
Below the diagonal: capsule_surface_model.recipe uses a module listed above it, which is the healthy direction.
capsule_surface_model.recipe uses capsule_surface_model.components, so a change to capsule_surface_model.components can break capsule_surface_model.recipe, while a change to capsule_surface_model.recipe can't break capsule_surface_model.components.
Position
Below the diagonal: capsule_surface_model.recipe uses a module listed above it, which is the healthy direction.
capsule_surface_model.recipe uses capsule_surface_model.bindings, so a change to capsule_surface_model.bindings can break capsule_surface_model.recipe, while a change to capsule_surface_model.recipe can't break capsule_surface_model.bindings.
Position
Below the diagonal: capsule_surface_model.recipe uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.console uses unicity_aos_bootstrap, so a change to unicity_aos_bootstrap can break unicity_aos_bootstrap.console, while a change to unicity_aos_bootstrap.console can't break unicity_aos_bootstrap.
Position
Below the diagonal: unicity_aos_bootstrap.console uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.console uses unicity_aos_bootstrap.updates, so a change to unicity_aos_bootstrap.updates can break unicity_aos_bootstrap.console, while a change to unicity_aos_bootstrap.console can't break unicity_aos_bootstrap.updates.
Position
Below the diagonal: unicity_aos_bootstrap.console uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.mcp.pending uses unicity_aos_bootstrap.mcp, so a change to unicity_aos_bootstrap.mcp can break unicity_aos_bootstrap.mcp.pending, while a change to unicity_aos_bootstrap.mcp.pending can't break unicity_aos_bootstrap.mcp.
Position
Below the diagonal: unicity_aos_bootstrap.mcp.pending uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.updates.oracle uses unicity_aos_bootstrap, so a change to unicity_aos_bootstrap can break unicity_aos_bootstrap.updates.oracle, while a change to unicity_aos_bootstrap.updates.oracle can't break unicity_aos_bootstrap.
Position
Below the diagonal: unicity_aos_bootstrap.updates.oracle uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.updates.oracle uses unicity_aos_bootstrap.updates, so a change to unicity_aos_bootstrap.updates can break unicity_aos_bootstrap.updates.oracle, while a change to unicity_aos_bootstrap.updates.oracle can't break unicity_aos_bootstrap.updates.
Position
Below the diagonal: unicity_aos_bootstrap.updates.oracle uses a module listed above it, which is the healthy direction.
adaptive_shell.input uses adaptive_shell.components, so a change to adaptive_shell.components can break adaptive_shell.input, while a change to adaptive_shell.input can't break adaptive_shell.components.
Position
Below the diagonal: adaptive_shell.input uses a module listed above it, which is the healthy direction.
adaptive_shell.input uses adaptive_shell.layout, so a change to adaptive_shell.layout can break adaptive_shell.input, while a change to adaptive_shell.input can't break adaptive_shell.layout.
Position
Below the diagonal: adaptive_shell.input uses a module listed above it, which is the healthy direction.
adaptive_shell.input uses adaptive_shell.theme, so a change to adaptive_shell.theme can break adaptive_shell.input, while a change to adaptive_shell.input can't break adaptive_shell.theme.
Position
Below the diagonal: adaptive_shell.input uses a module listed above it, which is the healthy direction.
adaptive_shell.input uses adaptive_shell.activity, so a change to adaptive_shell.activity can break adaptive_shell.input, while a change to adaptive_shell.input can't break adaptive_shell.activity.
Position
Below the diagonal: adaptive_shell.input uses a module listed above it, which is the healthy direction.
adaptive_shell.input uses adaptive_shell.atlas, so a change to adaptive_shell.atlas can break adaptive_shell.input, while a change to adaptive_shell.input can't break adaptive_shell.atlas.
Position
Below the diagonal: adaptive_shell.input uses a module listed above it, which is the healthy direction.
capsule_surface_model.a2ui uses capsule_surface_model.activity, so a change to capsule_surface_model.activity can break capsule_surface_model.a2ui, while a change to capsule_surface_model.a2ui can't break capsule_surface_model.activity.
Position
Below the diagonal: capsule_surface_model.a2ui uses a module listed above it, which is the healthy direction.
capsule_surface_model.a2ui uses capsule_surface_model.canonical, so a change to capsule_surface_model.canonical can break capsule_surface_model.a2ui, while a change to capsule_surface_model.a2ui can't break capsule_surface_model.canonical.
Position
Below the diagonal: capsule_surface_model.a2ui uses a module listed above it, which is the healthy direction.
capsule_surface_model.a2ui uses capsule_surface_model.components, so a change to capsule_surface_model.components can break capsule_surface_model.a2ui, while a change to capsule_surface_model.a2ui can't break capsule_surface_model.components.
Position
Below the diagonal: capsule_surface_model.a2ui uses a module listed above it, which is the healthy direction.
capsule_surface_model.a2ui uses capsule_surface_model.recipe, so a change to capsule_surface_model.recipe can break capsule_surface_model.a2ui, while a change to capsule_surface_model.a2ui can't break capsule_surface_model.recipe.
Position
Below the diagonal: capsule_surface_model.a2ui uses a module listed above it, which is the healthy direction.
capsule_surface_model.store uses capsule_surface_model.activity, so a change to capsule_surface_model.activity can break capsule_surface_model.store, while a change to capsule_surface_model.store can't break capsule_surface_model.activity.
Position
Below the diagonal: capsule_surface_model.store uses a module listed above it, which is the healthy direction.
capsule_surface_model.store uses capsule_surface_model.recipe, so a change to capsule_surface_model.recipe can break capsule_surface_model.store, while a change to capsule_surface_model.store can't break capsule_surface_model.recipe.
Position
Below the diagonal: capsule_surface_model.store uses a module listed above it, which is the healthy direction.
29→35 capsule_surface_model.store uses capsule_surface_model.fixturespart of a loop✕
Connections
1 pair of types, where a type in capsule_surface_model.store uses a type in capsule_surface_model.fixtures.
capsule_surface_model.store uses capsule_surface_model.fixtures, so a change to capsule_surface_model.fixtures can break capsule_surface_model.store, while a change to capsule_surface_model.store can't break capsule_surface_model.fixtures.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
capsule_surface_model.surface uses capsule_surface_model.components, so a change to capsule_surface_model.components can break capsule_surface_model.surface, while a change to capsule_surface_model.surface can't break capsule_surface_model.components.
Position
Below the diagonal: capsule_surface_model.surface uses a module listed above it, which is the healthy direction.
capsule_surface_model.surface uses capsule_surface_model.bindings, so a change to capsule_surface_model.bindings can break capsule_surface_model.surface, while a change to capsule_surface_model.surface can't break capsule_surface_model.bindings.
Position
Below the diagonal: capsule_surface_model.surface uses a module listed above it, which is the healthy direction.
capsule_surface_model.surface uses capsule_surface_model.recipe, so a change to capsule_surface_model.recipe can break capsule_surface_model.surface, while a change to capsule_surface_model.surface can't break capsule_surface_model.recipe.
Position
Below the diagonal: capsule_surface_model.surface uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.distro_trust uses unicity_aos_bootstrap, so a change to unicity_aos_bootstrap can break unicity_aos_bootstrap.distro_trust, while a change to unicity_aos_bootstrap.distro_trust can't break unicity_aos_bootstrap.
Position
Below the diagonal: unicity_aos_bootstrap.distro_trust uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.distro_trust uses unicity_aos_bootstrap.updates.oracle, so a change to unicity_aos_bootstrap.updates.oracle can break unicity_aos_bootstrap.distro_trust, while a change to unicity_aos_bootstrap.distro_trust can't break unicity_aos_bootstrap.updates.oracle.
Position
Below the diagonal: unicity_aos_bootstrap.distro_trust uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.mcp.interaction.tray uses unicity_aos_bootstrap.mcp.interaction.consent, so a change to unicity_aos_bootstrap.mcp.interaction.consent can break unicity_aos_bootstrap.mcp.interaction.tray, while a change to unicity_aos_bootstrap.mcp.interaction.tray can't break unicity_aos_bootstrap.mcp.interaction.consent.
Position
Below the diagonal: unicity_aos_bootstrap.mcp.interaction.tray uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.mcp.interaction.tray uses unicity_aos_bootstrap.mcp.interaction, so a change to unicity_aos_bootstrap.mcp.interaction can break unicity_aos_bootstrap.mcp.interaction.tray, while a change to unicity_aos_bootstrap.mcp.interaction.tray can't break unicity_aos_bootstrap.mcp.interaction.
Position
Below the diagonal: unicity_aos_bootstrap.mcp.interaction.tray uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.mcp.interaction.tray uses unicity_aos_bootstrap.updates.oracle, so a change to unicity_aos_bootstrap.updates.oracle can break unicity_aos_bootstrap.mcp.interaction.tray, while a change to unicity_aos_bootstrap.mcp.interaction.tray can't break unicity_aos_bootstrap.updates.oracle.
Position
Below the diagonal: unicity_aos_bootstrap.mcp.interaction.tray uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.migration uses unicity_aos_bootstrap, so a change to unicity_aos_bootstrap can break unicity_aos_bootstrap.migration, while a change to unicity_aos_bootstrap.migration can't break unicity_aos_bootstrap.
Position
Below the diagonal: unicity_aos_bootstrap.migration uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.migration uses unicity_aos_bootstrap.mcp.pending, so a change to unicity_aos_bootstrap.mcp.pending can break unicity_aos_bootstrap.migration, while a change to unicity_aos_bootstrap.migration can't break unicity_aos_bootstrap.mcp.pending.
Position
Below the diagonal: unicity_aos_bootstrap.migration uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.migration uses unicity_aos_bootstrap.updates.oracle, so a change to unicity_aos_bootstrap.updates.oracle can break unicity_aos_bootstrap.migration, while a change to unicity_aos_bootstrap.migration can't break unicity_aos_bootstrap.updates.oracle.
Position
Below the diagonal: unicity_aos_bootstrap.migration uses a module listed above it, which is the healthy direction.
adaptive_shell.fixtures uses adaptive_shell.components, so a change to adaptive_shell.components can break adaptive_shell.fixtures, while a change to adaptive_shell.fixtures can't break adaptive_shell.components.
Position
Below the diagonal: adaptive_shell.fixtures uses a module listed above it, which is the healthy direction.
adaptive_shell.fixtures uses adaptive_shell.layout, so a change to adaptive_shell.layout can break adaptive_shell.fixtures, while a change to adaptive_shell.fixtures can't break adaptive_shell.layout.
Position
Below the diagonal: adaptive_shell.fixtures uses a module listed above it, which is the healthy direction.
adaptive_shell.fixtures uses adaptive_shell.theme, so a change to adaptive_shell.theme can break adaptive_shell.fixtures, while a change to adaptive_shell.fixtures can't break adaptive_shell.theme.
Position
Below the diagonal: adaptive_shell.fixtures uses a module listed above it, which is the healthy direction.
adaptive_shell.fixtures uses adaptive_shell.activity, so a change to adaptive_shell.activity can break adaptive_shell.fixtures, while a change to adaptive_shell.fixtures can't break adaptive_shell.activity.
Position
Below the diagonal: adaptive_shell.fixtures uses a module listed above it, which is the healthy direction.
adaptive_shell.fixtures uses adaptive_shell.reconcile, so a change to adaptive_shell.reconcile can break adaptive_shell.fixtures, while a change to adaptive_shell.fixtures can't break adaptive_shell.reconcile.
Position
Below the diagonal: adaptive_shell.fixtures uses a module listed above it, which is the healthy direction.
adaptive_shell.fixtures uses adaptive_shell.atlas, so a change to adaptive_shell.atlas can break adaptive_shell.fixtures, while a change to adaptive_shell.fixtures can't break adaptive_shell.atlas.
Position
Below the diagonal: adaptive_shell.fixtures uses a module listed above it, which is the healthy direction.
adaptive_shell.fixtures uses adaptive_shell.input, so a change to adaptive_shell.input can break adaptive_shell.fixtures, while a change to adaptive_shell.fixtures can't break adaptive_shell.input.
Position
Below the diagonal: adaptive_shell.fixtures uses a module listed above it, which is the healthy direction.
capsule_surface_model.fixtures uses capsule_surface_model.activity, so a change to capsule_surface_model.activity can break capsule_surface_model.fixtures, while a change to capsule_surface_model.fixtures can't break capsule_surface_model.activity.
Position
Below the diagonal: capsule_surface_model.fixtures uses a module listed above it, which is the healthy direction.
capsule_surface_model.fixtures uses capsule_surface_model.components, so a change to capsule_surface_model.components can break capsule_surface_model.fixtures, while a change to capsule_surface_model.fixtures can't break capsule_surface_model.components.
Position
Below the diagonal: capsule_surface_model.fixtures uses a module listed above it, which is the healthy direction.
capsule_surface_model.fixtures uses capsule_surface_model.bindings, so a change to capsule_surface_model.bindings can break capsule_surface_model.fixtures, while a change to capsule_surface_model.fixtures can't break capsule_surface_model.bindings.
Position
Below the diagonal: capsule_surface_model.fixtures uses a module listed above it, which is the healthy direction.
capsule_surface_model.fixtures uses capsule_surface_model.recipe, so a change to capsule_surface_model.recipe can break capsule_surface_model.fixtures, while a change to capsule_surface_model.fixtures can't break capsule_surface_model.recipe.
Position
Below the diagonal: capsule_surface_model.fixtures uses a module listed above it, which is the healthy direction.
capsule_surface_model.fixtures uses capsule_surface_model.store, so a change to capsule_surface_model.store can break capsule_surface_model.fixtures, while a change to capsule_surface_model.fixtures can't break capsule_surface_model.store.
Position
Below the diagonal: capsule_surface_model.fixtures uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.documents uses capsule_surface_model.recipe, so a change to capsule_surface_model.recipe can break capsule_workspace_recipes.documents, while a change to capsule_workspace_recipes.documents can't break capsule_surface_model.recipe.
Position
Below the diagonal: capsule_workspace_recipes.documents uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.documents uses capsule_surface_model.store, so a change to capsule_surface_model.store can break capsule_workspace_recipes.documents, while a change to capsule_workspace_recipes.documents can't break capsule_surface_model.store.
Position
Below the diagonal: capsule_workspace_recipes.documents uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.main uses unicity_aos_bootstrap, so a change to unicity_aos_bootstrap can break unicity_aos_bootstrap.main, while a change to unicity_aos_bootstrap.main can't break unicity_aos_bootstrap.
Position
Below the diagonal: unicity_aos_bootstrap.main uses a module listed above it, which is the healthy direction.
unicity_aos_bootstrap.main uses unicity_aos_bootstrap.distro_trust, so a change to unicity_aos_bootstrap.distro_trust can break unicity_aos_bootstrap.main, while a change to unicity_aos_bootstrap.main can't break unicity_aos_bootstrap.distro_trust.
Position
Below the diagonal: unicity_aos_bootstrap.main uses a module listed above it, which is the healthy direction.
adaptive_shell.main uses adaptive_shell.theme, so a change to adaptive_shell.theme can break adaptive_shell.main, while a change to adaptive_shell.main can't break adaptive_shell.theme.
Position
Below the diagonal: adaptive_shell.main uses a module listed above it, which is the healthy direction.
adaptive_shell.main uses adaptive_shell.fixtures, so a change to adaptive_shell.fixtures can break adaptive_shell.main, while a change to adaptive_shell.main can't break adaptive_shell.fixtures.
Position
Below the diagonal: adaptive_shell.main uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.service uses capsule_surface_model.activity, so a change to capsule_surface_model.activity can break capsule_workspace_recipes.service, while a change to capsule_workspace_recipes.service can't break capsule_surface_model.activity.
Position
Below the diagonal: capsule_workspace_recipes.service uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.service uses capsule_workspace_recipes.policy, so a change to capsule_workspace_recipes.policy can break capsule_workspace_recipes.service, while a change to capsule_workspace_recipes.service can't break capsule_workspace_recipes.policy.
Position
Below the diagonal: capsule_workspace_recipes.service uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.service uses capsule_surface_model.recipe, so a change to capsule_surface_model.recipe can break capsule_workspace_recipes.service, while a change to capsule_workspace_recipes.service can't break capsule_surface_model.recipe.
Position
Below the diagonal: capsule_workspace_recipes.service uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.service uses capsule_surface_model.store, so a change to capsule_surface_model.store can break capsule_workspace_recipes.service, while a change to capsule_workspace_recipes.service can't break capsule_surface_model.store.
Position
Below the diagonal: capsule_workspace_recipes.service uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.service uses capsule_workspace_recipes.documents, so a change to capsule_workspace_recipes.documents can break capsule_workspace_recipes.service, while a change to capsule_workspace_recipes.service can't break capsule_workspace_recipes.documents.
Position
Below the diagonal: capsule_workspace_recipes.service uses a module listed above it, which is the healthy direction.
39→40 capsule_workspace_recipes.service uses capsule_workspace_recipes.backendpart of a loop✕
Connections
5 pairs of types, where a type in capsule_workspace_recipes.service uses a type in capsule_workspace_recipes.backend.
capsule_workspace_recipes.service uses capsule_workspace_recipes.backend, so a change to capsule_workspace_recipes.backend can break capsule_workspace_recipes.service, while a change to capsule_workspace_recipes.service can't break capsule_workspace_recipes.backend.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
capsule_workspace_recipes.backend uses capsule_workspace_recipes.documents, so a change to capsule_workspace_recipes.documents can break capsule_workspace_recipes.backend, while a change to capsule_workspace_recipes.backend can't break capsule_workspace_recipes.documents.
Position
Below the diagonal: capsule_workspace_recipes.backend uses a module listed above it, which is the healthy direction.
capsule_workspace_recipes.backend uses capsule_workspace_recipes.service, so a change to capsule_workspace_recipes.service can break capsule_workspace_recipes.backend, while a change to capsule_workspace_recipes.backend can't break capsule_workspace_recipes.service.
Position
Below the diagonal: capsule_workspace_recipes.backend uses a module listed above it, which is the healthy direction.
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
10
Medium
A05:2025 — Injection
1
Medium
Roadmap
Top priorities: Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; 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.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
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.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Bring the 39 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ShellState::apply_with_context (cyclomatic 38), unicity_aos_bootstrap::console::run_inner (cyclomatic 34), unicity_aos_bootstrap::mcp::serve (cyclomatic 33).
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 — 0
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 — 298
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 — 33
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 22
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 45 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 — 45 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, 314 of 331 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.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in apps/aos-tray produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 184 commit(s) sampled, automation and bot accounts excluded). One of them holds 97% of the history; the other 3 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
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.
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 — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
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 ToolchainServer (crates/unicity-aos-bootstrap). the service did not build — `cargo build --locked --bin 'unicity-aos-bootstrap'` exited 1: info: syncing channel updates for 1.95.0-x86_64-unknown-linux-gnu
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-1.95.0.toml.sha256' to '/usr/local/rustup/tmp/fdmr…; runtime evidence skipped (launch chosen because 'axum' dependency in crates/unicity-aos-bootstrap/Cargo.toml, binary 'unicity-aos-bootstrap', started with its 'serve' subcommand).
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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, 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.
X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, 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.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — 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.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust, Swift is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
39 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ShellState::apply_with_context at 38. A further 9 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 PrimitiveRecord::for_primitive at 41 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: capsules/capsule-surface-catalog/src/catalog.rs (PrimitiveRecord::for_primitive at 41), capsules/capsule-rhai/src/lib.rs (FailureCode::as_str at 20), apps/adaptive-shell/src/components.rs (ComponentKind::contract at 19), capsules/capsule-surface-model/src/components.rs (ComponentKind::contract at 19), capsules/capsule-surface-catalog/src/lab.rs (capsule_surface_catalog::lab::token_role at 18). 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.
+ 23 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 39 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ShellState::apply_with_context (cyclomatic 38), unicity_aos_bootstrap::console::run_inner (cyclomatic 34), unicity_aos_bootstrap::mcp::serve (cyclomatic 33). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 39 together lifts Cyclomatic Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 37 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with unicity_aos_bootstrap::console::run_inner (cognitive 76), unicity_aos_bootstrap::console::view::draw (cognitive 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.2 to about 5.6/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.5 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 14 FileTooLong finding(s) in God Classes — start with lib.rs (4), mod.rs (2), components.rs (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 6 FunctionTooLong finding(s) in God Classes — start with mod.rs (2), broker.rs, view.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with lib.rs, store.rs, service.rs. — 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.
89 duplicated block group(s) detected. 5.5 % of the production lines (3,725 of 68,297) are in a reported copy. A further 51 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 7 of the 140 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.
+ 60 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with lib.rs (3), theme.rs, activity.rs. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 9 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with activity.rs, theme.rs, selection.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with approval.rs (2), host_hooks.rs, lib.rs. — One of this dimension's main actionable groups (8 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.2 / 10Stronggated by 3 serious findings✓ 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.
32 production modules (Cargo+SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence.
Off the main sequence: aos-mcp-broker · ×3
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 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.
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
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.
Secret scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
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 310 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. This repository publishes itself under MIT OR Apache-2.0, which is its own choice and is not judged here.
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: crates/unicity-aos-bootstrap/src/main.rs (17×28=476); crates/unicity-aos-bootstrap/src/mcp/mod.rs (5×33=165); crates/aos-mcp-broker/src/broker.rs (3×17=51) Repeated repair below the complexity floor: crates/unicity-aos-bootstrap/src/lib.rs (9 of 13 changes were fixes); crates/aos-mcp-broker/src/approval.rs (3 of 3 changes were fixes)
Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs, mod.rs, broker.rs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with lib.rs, approval.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_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.
1 deducted task-comment markers across 68297 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
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. 31 document(s) read across 1 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.
No ADRs foundcrates/unicity-aos-bootstrap/Cargo.toml:41
What to do
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — 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 any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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).
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep hit a parse error in 3 file(s) — `crates/unicity-aos-bootstrap/src/mcp/interaction/tray.rs` (line 323, lines 334–335, line 354, …), `install.sh` (lines 768–769, line 892, line 1494), `scripts/test-upgrade-self-heal.sh` — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 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
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-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.
Resolve the 4 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-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.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 171 of the 209 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
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.
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).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with rust-toolchain.toml. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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 · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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 · Observability7.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 16/19 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/adaptive-shell`, `apps/aos-tray`, `crates/unicity-aos-bootstrap`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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.
What to do
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.
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.
`run` is async and calls .waitUntilExit() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — apps/aos-tray/Sources/AOSTrayCore/UpdateInventory.swift:103
What to do
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
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.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
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.
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.
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.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 14 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.
X9 Subsumed condition operand — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: 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.
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.
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 — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the service did not build — `cargo build --locked --bin 'unicity-aos-bootstrap'` exited 1: info: syncing channel updates for 1.95.0-x86_64-unknown-linux-gnu
error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-1.95.0.toml.sha256' to '/usr/local/rustup/tmp/fdmr…; runtime evidence skipped (launch chosen because 'axum' dependency in crates/unicity-aos-bootstrap/Cargo.toml, binary 'unicity-aos-bootstrap', started with its 'serve' subcommand) 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.
D10 Test Quality — ~14035 lines of test source are present (.py, .rs, .swift) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — N/A — too few peers to establish a naming convention (6974 declarations, no unit with a dominant convention).
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust, Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .rs, .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
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 — Swift suite
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 11 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
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 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
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'.
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Python, Rust, Swift source (service entry point: crates/unicity-aos-bootstrap/src/health.rs:74 (Router::new()))
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 `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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.
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.
X12 Unreachable branch — X12 reached only 4% of this repository's production lines — rust (59,526 lines), swift (5,842 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — X13 reached only 4% of this repository's production lines — rust (59,526 lines), swift (5,842 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — 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
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 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
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — 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
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — X3 reached only 13% of this repository's production lines — rust (59,526 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
X5 Nullable reference types — 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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
unicity_aos_bootstrap::console::run_inner (cognitive 76) crates/unicity-aos-bootstrap/src/console/mod.rs:343— unicity_aos_bootstrap::console::run_inner has cognitive complexity 76 (threshold 15). Drivers by points: if/else 17 (51 pts), match/switch 5 (16 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 47). 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.
unicity_aos_bootstrap::console::view::draw (cognitive 62) crates/unicity-aos-bootstrap/src/console/view.rs:17— unicity_aos_bootstrap::console::view::draw has cognitive complexity 62 (threshold 15). Drivers by points: if/else 34 (52 pts), loops 3 (6 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
unicity_aos_bootstrap::mcp::serve (cognitive 57) crates/unicity-aos-bootstrap/src/mcp/mod.rs:335— unicity_aos_bootstrap::mcp::serve has cognitive complexity 57 (threshold 15). Drivers by points: if/else 9 (25 pts), match/switch 8 (24 pts), boolean chains 4, loops 2 (4 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.
unicity_aos_bootstrap::handle_distro_apply (cognitive 40) crates/unicity-aos-bootstrap/src/main.rs:984— unicity_aos_bootstrap::handle_distro_apply has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (30 pts), match/switch 6 (8 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.
unicity_aos_bootstrap::migration::archive_inactive_activation_state (cognitive 31) crates/unicity-aos-bootstrap/src/migration.rs:331— unicity_aos_bootstrap::migration::archive_inactive_activation_state has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 4 (6 pts), boolean chains 4, match/switch 2 (3 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.
unicity_aos_bootstrap::updates::oracle::check (cognitive 27) crates/unicity-aos-bootstrap/src/updates/oracle.rs:135— unicity_aos_bootstrap::updates::oracle::check has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 2 (6 pts), boolean chains 1, 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.
unicity_aos_bootstrap::native_setup::canonical_setup_home (cognitive 26) crates/unicity-aos-bootstrap/src/native_setup/mod.rs:105— unicity_aos_bootstrap::native_setup::canonical_setup_home has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 3 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
unicity_aos_bootstrap::console::native::connect (cognitive 25) crates/unicity-aos-bootstrap/src/console/native.rs:52— unicity_aos_bootstrap::console::native::connect has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 7, match/switch 2 (5 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.
unicity_aos_bootstrap::mcp::intercept_downstream (cognitive 19) crates/unicity-aos-bootstrap/src/mcp/mod.rs:802— unicity_aos_bootstrap::mcp::intercept_downstream has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3 (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.
unicity_aos_bootstrap::version::parse_release (cognitive 19) crates/unicity-aos-bootstrap/src/version.rs:38— unicity_aos_bootstrap::version::parse_release has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4 (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.
unicity_aos_bootstrap::leading_runtime_root_index (cognitive 18) crates/unicity-aos-bootstrap/src/main.rs:760— unicity_aos_bootstrap::leading_runtime_root_index has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, 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.
unicity_aos_bootstrap::updates::capsules::check (cognitive 18) crates/unicity-aos-bootstrap/src/updates/capsules.rs:23— unicity_aos_bootstrap::updates::capsules::check has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, boolean chains 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.
unicity_aos_bootstrap::handle_runtime_stop (cognitive 17) crates/unicity-aos-bootstrap/src/main.rs:614— unicity_aos_bootstrap::handle_runtime_stop has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, match/switch 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
unicity_aos_bootstrap::mcp::prepare_client_message (cognitive 17) crates/unicity-aos-bootstrap/src/mcp/mod.rs:733— unicity_aos_bootstrap::mcp::prepare_client_message has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 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.
unicity_aos_bootstrap::updates::run (cognitive 17) crates/unicity-aos-bootstrap/src/updates/mod.rs:457— unicity_aos_bootstrap::updates::run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 1 (3 pts), match/switch 2 (nesting depth added 6). 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.
unicity_aos_bootstrap::distro_trust::write_private_atomic (cognitive 16) crates/unicity-aos-bootstrap/src/distro_trust.rs:581— unicity_aos_bootstrap::distro_trust::write_private_atomic has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4 (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.
unicity_aos_bootstrap::handle_product_command (cognitive 16) crates/unicity-aos-bootstrap/src/main.rs:334— unicity_aos_bootstrap::handle_product_command has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, match/switch 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.
FileTooLong: src/lib.rs capsules/capsule-react/src/lib.rs— FileTooLong — 987 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: ReactLoop (2 blocks, 529-2079). The bar is 500 significant lines; this is 487 over it, 1.97× 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: src/main.rs crates/unicity-aos-bootstrap/src/main.rs— FileTooLong — 934 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 36 free functions. The bar is 500 significant lines; this is 434 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: src/theme.rs capsules/capsule-surface-catalog/src/theme.rs— FileTooLong — 870 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 370 over it, 1.74× 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: src/migration.rs crates/unicity-aos-bootstrap/src/migration.rs— FileTooLong — 858 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 43 free functions. The bar is 500 significant lines; this is 358 over it, 1.72× 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: src/lib.rs capsules/capsule-session/src/lib.rs— FileTooLong — 755 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 255 over it, 1.51× 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: mcp/mod.rs crates/unicity-aos-bootstrap/src/mcp/mod.rs— FileTooLong — 719 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 219 over it, 1.44× 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: src/service.rs capsules/capsule-workspace-recipes/src/service.rs— FileTooLong — 597 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 73% of them inside a single declaration: RecipeService (2 blocks, 104-648). The bar is 500 significant lines; this is 97 over it, 1.19× 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: src/components.rs capsules/capsule-surface-model/src/components.rs— FileTooLong — 575 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 75 over it, 1.15× 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: src/components.rs apps/adaptive-shell/src/components.rs— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 74 over it, 1.15× 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: src/store.rs capsules/capsule-surface-model/src/store.rs— FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 74 over it, 1.15× 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: src/activity.rs apps/adaptive-shell/src/activity.rs— FileTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 68 over it, 1.14× 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: src/lib.rs capsules/capsule-rhai/src/lib.rs— FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 62 over it, 1.12× 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: native_setup/mod.rs crates/unicity-aos-bootstrap/src/native_setup/mod.rs— FileTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 46 over it, 1.09× 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: src/lib.rs crates/unicity-aos-bootstrap/src/lib.rs— FileTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 41 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (8 lines × 2) capsules/capsule-surface-catalog/src/theme.rs:728— capsules/capsule-surface-catalog/src/theme.rs:728-735 | capsules/capsule-surface-catalog/src/theme.rs:752-759 — 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 `capsules/capsule-surface-catalog/src/theme.rs:728` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) capsules/capsule-surface-model/src/activity.rs:23— capsules/capsule-surface-model/src/activity.rs:23-30 | capsules/capsule-surface-model/src/activity.rs:75-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) capsules/capsule-workspace-recipes/src/service.rs:265— capsules/capsule-workspace-recipes/src/service.rs:265-272 | capsules/capsule-workspace-recipes/src/service.rs:333-340 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `capsules/capsule-workspace-recipes/src/service.rs:332` calls `authorize` and `capsules/capsule-workspace-recipes/src/service.rs:264` 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) crates/unicity-aos-bootstrap/src/mcp/mod.rs:498— crates/unicity-aos-bootstrap/src/mcp/mod.rs:498-505 | crates/unicity-aos-bootstrap/src/mcp/mod.rs:513-520 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) capsules/capsule-users/src/store.rs:239— capsules/capsule-users/src/store.rs:239-246 | capsules/capsule-users/src/store.rs:456-463 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) capsules/capsule-openai-compat/src/lib.rs:171— capsules/capsule-openai-compat/src/lib.rs:171-178 | capsules/capsule-openai/src/lib.rs:121-128 — before extracting anything, compare `capsules/capsule-openai-compat/src/lib.rs` and `capsules/capsule-openai/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) capsules/capsule-surface-model/src/surface.rs:9— capsules/capsule-surface-model/src/surface.rs:9-16 | capsules/capsule-workspace-recipes/src/policy.rs:115-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/aos-mcp-broker/src/cache.rs:142— crates/aos-mcp-broker/src/cache.rs:142-150 | crates/aos-mcp-broker/src/cache.rs:192-199 — 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 `crates/aos-mcp-broker/src/cache.rs:142` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/unicity-aos-bootstrap/src/migration.rs:620— crates/unicity-aos-bootstrap/src/migration.rs:620-627 | crates/unicity-aos-bootstrap/src/migration.rs:661-668 — 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 `crates/unicity-aos-bootstrap/src/migration.rs:620` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) capsules/capsule-users/src/lib.rs:325— capsules/capsule-users/src/lib.rs:325-332 | capsules/capsule-users/src/lib.rs:437-444 — 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 `capsules/capsule-users/src/lib.rs:325` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) capsules/capsule-openai-compat/src/lib.rs:579— capsules/capsule-openai-compat/src/lib.rs:579-586 | capsules/capsule-openai/src/lib.rs:505-512 — before extracting anything, compare `capsules/capsule-openai-compat/src/lib.rs` and `capsules/capsule-openai/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-openai-compat/src/lib.rs:579` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:244— apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:244-251 | apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:265-272 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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) apps/adaptive-shell/src/activity.rs:870— apps/adaptive-shell/src/activity.rs:870-879 | capsules/capsule-surface-model/src/store.rs:714-723 — before extracting anything, compare `apps/adaptive-shell/src/activity.rs` and `capsules/capsule-surface-model/src/store.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) apps/adaptive-shell/src/theme.rs:315— apps/adaptive-shell/src/theme.rs:315-324 | capsules/capsule-surface-catalog/src/theme.rs:1208-1217 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 2) capsules/capsule-registry/src/selection.rs:137— capsules/capsule-registry/src/selection.rs:137-146 | capsules/capsule-registry/src/selection.rs:155-164 — 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 `capsules/capsule-registry/src/selection.rs:137` 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) capsules/capsule-workspace-recipes/src/service.rs:335— capsules/capsule-workspace-recipes/src/service.rs:335-344 | capsules/capsule-workspace-recipes/src/service.rs:437-446 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `capsules/capsule-workspace-recipes/src/service.rs:332` calls `authorize`, `scan_for_forbidden_content`, `validate` and `capsules/capsule-workspace-recipes/src/service.rs:436` 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 (10 lines × 2) crates/unicity-aos-bootstrap/src/cli/principals.rs:36— crates/unicity-aos-bootstrap/src/cli/principals.rs:36-45 | crates/unicity-aos-bootstrap/src/cli/status.rs:41-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/unicity-aos-bootstrap/src/cli/principals.rs:36` 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) crates/unicity-aos-bootstrap/src/mcp/mod.rs:571— crates/unicity-aos-bootstrap/src/mcp/mod.rs:571-582 | crates/unicity-aos-bootstrap/src/mcp/mod.rs:591-600 — 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 `crates/unicity-aos-bootstrap/src/mcp/mod.rs:571` 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) apps/adaptive-shell/src/components.rs:720— apps/adaptive-shell/src/components.rs:720-729 | capsules/capsule-surface-model/src/components.rs:591-600 — before extracting anything, compare `apps/adaptive-shell/src/components.rs` and `capsules/capsule-surface-model/src/components.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:288— apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:288-297 | apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:175-184 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (10 lines × 2) scripts/capsule_release.py:185— scripts/capsule_release.py:185-194 | scripts/validate-runtime-archive.py:18-27 — 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 (9 lines × 2) capsules/capsule-mcp/src/host_hooks.rs:348— capsules/capsule-mcp/src/host_hooks.rs:348-356 | crates/unicity-aos-bootstrap/src/hook.rs:294-302 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) capsules/capsule-react/src/lib.rs:1011— capsules/capsule-react/src/lib.rs:1011-1019 | capsules/capsule-react/src/lib.rs:1119-1127 — 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 `capsules/capsule-react/src/lib.rs:1011` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) crates/aos-mcp-broker/src/approval.rs:893— crates/aos-mcp-broker/src/approval.rs:893-901 | crates/aos-mcp-broker/src/approval.rs:907-915 — 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 `crates/aos-mcp-broker/src/approval.rs:893` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9 lines × 2) crates/aos-mcp-broker/src/execute.rs:246— crates/aos-mcp-broker/src/execute.rs:246-254 | crates/aos-mcp-broker/src/execute.rs:275-283 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/aos-mcp-broker/src/approval.rs:491— crates/aos-mcp-broker/src/approval.rs:491-499 | crates/aos-mcp-broker/src/approval.rs:844-852 — 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 `crates/aos-mcp-broker/src/approval.rs:491` 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) crates/unicity-aos-bootstrap/src/cli/native_setup.rs:34— crates/unicity-aos-bootstrap/src/cli/native_setup.rs:34-42 | crates/unicity-aos-bootstrap/src/main.rs:901-909 — 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 `crates/unicity-aos-bootstrap/src/cli/native_setup.rs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/unicity-aos-bootstrap/src/migration.rs:156— crates/unicity-aos-bootstrap/src/migration.rs:156-164 | crates/unicity-aos-bootstrap/src/migration.rs:693-701 — 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 `crates/unicity-aos-bootstrap/src/migration.rs:156` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) scripts/check_glibc.py:35— scripts/check_glibc.py:35-43 | scripts/check_static_elf.py:53-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `scripts/check_glibc.py:35` 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 (7 lines × 2) capsules/capsule-context-engine/src/lib.rs:537— capsules/capsule-context-engine/src/lib.rs:537-543 | capsules/capsule-prompt-builder/src/lib.rs:372-378 — 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 `capsules/capsule-context-engine/src/lib.rs:537` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/unicity-aos-bootstrap/src/distro_trust.rs:504— crates/unicity-aos-bootstrap/src/distro_trust.rs:504-510 | crates/unicity-aos-bootstrap/src/distro_trust.rs:521-527 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/unicity-aos-bootstrap/src/updates/mod.rs:157— crates/unicity-aos-bootstrap/src/updates/mod.rs:157-163 | crates/unicity-aos-bootstrap/src/updates/process.rs:88-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 `crates/unicity-aos-bootstrap/src/updates/mod.rs:157` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) apps/adaptive-shell/src/components.rs:732— apps/adaptive-shell/src/components.rs:732-738 | capsules/capsule-surface-model/src/components.rs:602-608 — before extracting anything, compare `apps/adaptive-shell/src/components.rs` and `capsules/capsule-surface-model/src/components.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) capsules/capsule-hook-adapter-oracle/src/lib.rs:223— capsules/capsule-hook-adapter-oracle/src/lib.rs:223-229 | capsules/capsule-mcp/src/host_hooks.rs:369-375 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/aos-mcp-broker/src/discovery.rs:482— crates/aos-mcp-broker/src/discovery.rs:482-488 | crates/aos-mcp-broker/src/execute.rs:706-712 — 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 (7 lines × 2) capsules/capsule-system/src/lib.rs:160— capsules/capsule-system/src/lib.rs:160-166 | capsules/capsule-system/src/lib.rs:206-212 — 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 `capsules/capsule-system/src/lib.rs:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) crates/unicity-aos-bootstrap/src/updates/oracle.rs:44— crates/unicity-aos-bootstrap/src/updates/oracle.rs:44-50 | crates/unicity-aos-bootstrap/src/updates/process.rs:90-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/unicity-aos-bootstrap/src/updates/oracle.rs:44` 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 (6 lines × 2) crates/unicity-aos-bootstrap/src/migration.rs:345— crates/unicity-aos-bootstrap/src/migration.rs:345-350 | crates/unicity-aos-bootstrap/src/migration.rs:386-391 — 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 `crates/unicity-aos-bootstrap/src/migration.rs:345` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) apps/adaptive-shell/src/components.rs:333— apps/adaptive-shell/src/components.rs:333-338 | capsules/capsule-surface-model/src/components.rs:255-260 — before extracting anything, compare `apps/adaptive-shell/src/components.rs` and `capsules/capsule-surface-model/src/components.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) capsules/capsule-context-engine/src/lib.rs:182— capsules/capsule-context-engine/src/lib.rs:182-187 | capsules/capsule-prompt-builder/src/lib.rs:87-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) capsules/capsule-forge/src/lib.rs:205— capsules/capsule-forge/src/lib.rs:205-210 | capsules/capsule-system/src/lib.rs:98-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) capsules/capsule-hook-adapter-oracle/src/lib.rs:231— capsules/capsule-hook-adapter-oracle/src/lib.rs:231-236 | capsules/capsule-mcp/src/host_hooks.rs:377-382 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) capsules/capsule-meta-harness/src/lib.rs:35— capsules/capsule-meta-harness/src/lib.rs:35-40 | capsules/capsule-surface-model/src/canonical.rs:190-195 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/aos-mcp-broker/src/cache.rs:253— crates/aos-mcp-broker/src/cache.rs:253-258 | crates/aos-mcp-broker/src/discovery.rs:559-564 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:369— apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:369-374 | apps/aos-tray/Sources/AOSTrayCore/MountedVolume.swift:35-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
unicity_aos_bootstrap::console::run_inner (cyclomatic 34) crates/unicity-aos-bootstrap/src/console/mod.rs:343— unicity_aos_bootstrap::console::run_inner has cyclomatic complexity 34 (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.
unicity_aos_bootstrap::mcp::serve (cyclomatic 33) crates/unicity-aos-bootstrap/src/mcp/mod.rs:335— unicity_aos_bootstrap::mcp::serve has cyclomatic complexity 33 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
unicity_aos_bootstrap::console::view::draw (cyclomatic 28) crates/unicity-aos-bootstrap/src/console/view.rs:17— unicity_aos_bootstrap::console::view::draw has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
unicity_aos_bootstrap::handle_product_command (cyclomatic 28) crates/unicity-aos-bootstrap/src/main.rs:334— unicity_aos_bootstrap::handle_product_command has cyclomatic complexity 28 (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.
unicity_aos_bootstrap::handle_distro_apply (cyclomatic 24) crates/unicity-aos-bootstrap/src/main.rs:984— unicity_aos_bootstrap::handle_distro_apply 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.
unicity_aos_bootstrap::migration::archive_inactive_activation_state (cyclomatic 22) crates/unicity-aos-bootstrap/src/migration.rs:331— unicity_aos_bootstrap::migration::archive_inactive_activation_state 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.
unicity_aos_bootstrap::console::native::connect (cyclomatic 19) crates/unicity-aos-bootstrap/src/console/native.rs:52— unicity_aos_bootstrap::console::native::connect 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.
aos_mcp_broker::approval::handle_mcp_ingress_respond (cognitive 28) crates/aos-mcp-broker/src/approval.rs:640— aos_mcp_broker::approval::handle_mcp_ingress_respond has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (24 pts), match/switch 3 (4 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.
aos_mcp_broker::broker::handle_mcp_call (cognitive 25) crates/aos-mcp-broker/src/broker.rs:203— aos_mcp_broker::broker::handle_mcp_call has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (20 pts), match/switch 4 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aos_mcp_broker::execute::dispatch_with_approval (cognitive 22) crates/aos-mcp-broker/src/execute.rs:142— aos_mcp_broker::execute::dispatch_with_approval has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 7 (9 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aos_mcp_broker::approval::handle_mcp_grant_respond (cognitive 16) crates/aos-mcp-broker/src/approval.rs:822— aos_mcp_broker::approval::handle_mcp_grant_respond has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aos_mcp_broker::approval::result::resolve_with_decision (cognitive 16) crates/aos-mcp-broker/src/approval/result.rs:18— aos_mcp_broker::approval::result::resolve_with_decision has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 4 (5 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aos_mcp_broker::policy::validate (cognitive 16) crates/aos-mcp-broker/src/policy.rs:299— aos_mcp_broker::policy::validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, loops 2 (3 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.
FunctionTooLong: aos_mcp_broker::broker::handle_mcp_call crates/aos-mcp-broker/src/broker.rs:203— FunctionTooLong — aos_mcp_broker::broker::handle_mcp_call runs 251 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 151 over it, 2.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: unicity_aos_bootstrap::mcp::serve crates/unicity-aos-bootstrap/src/mcp/mod.rs:335— FunctionTooLong — unicity_aos_bootstrap::mcp::serve runs 241 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: unicity_aos_bootstrap::console::view::draw crates/unicity-aos-bootstrap/src/console/view.rs:17— FunctionTooLong — unicity_aos_bootstrap::console::view::draw runs 231 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: capsule_surface_catalog::theme::palette capsules/capsule-surface-catalog/src/theme.rs:896— FunctionTooLong — capsule_surface_catalog::theme::palette runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: unicity_aos_bootstrap::console::run_inner crates/unicity-aos-bootstrap/src/console/mod.rs:343— FunctionTooLong — unicity_aos_bootstrap::console::run_inner runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: unicity_aos_bootstrap::distro_trust::verify_release_directory crates/unicity-aos-bootstrap/src/distro_trust.rs:97— FunctionTooLong — unicity_aos_bootstrap::distro_trust::verify_release_directory runs 102 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (11 lines × 2) capsules/capsule-users/src/lib.rs:198— capsules/capsule-users/src/lib.rs:198-208 | capsules/capsule-users/src/lib.rs:221-231 — 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 `capsules/capsule-users/src/lib.rs:198` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/unicity-aos-bootstrap/src/cli/principals.rs:61— crates/unicity-aos-bootstrap/src/cli/principals.rs:61-71 | crates/unicity-aos-bootstrap/src/cli/status.rs:72-82 — 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 `crates/unicity-aos-bootstrap/src/cli/principals.rs:61` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) crates/unicity-aos-bootstrap/src/lib.rs:759— crates/unicity-aos-bootstrap/src/lib.rs:759-769 | crates/unicity-aos-bootstrap/src/migration.rs:456-466 — 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 `crates/unicity-aos-bootstrap/src/lib.rs:759` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/aos-mcp-broker/src/broker.rs:145— crates/aos-mcp-broker/src/broker.rs:145-157 | crates/aos-mcp-broker/src/broker.rs:205-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/aos-mcp-broker/src/broker.rs:145` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) apps/adaptive-shell/src/fixtures.rs:822— apps/adaptive-shell/src/fixtures.rs:822-832 | apps/adaptive-shell/src/fixtures.rs:1119-1129 — 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) crates/unicity-aos-bootstrap/src/legacy_private_permissions.rs:29— crates/unicity-aos-bootstrap/src/legacy_private_permissions.rs:29-33 | crates/unicity-aos-bootstrap/src/migration.rs:823-827 — 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) capsules/capsule-registry/src/lib.rs:545— capsules/capsule-registry/src/lib.rs:545-549 | capsules/capsule-registry/src/lib.rs:674-681 — 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 `capsules/capsule-registry/src/lib.rs:545` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) crates/unicity-aos-bootstrap/src/status/mounted_volume.rs:59— crates/unicity-aos-bootstrap/src/status/mounted_volume.rs:59-63 | crates/unicity-aos-bootstrap/src/updates/process.rs:89-94 — 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 `crates/unicity-aos-bootstrap/src/status/mounted_volume.rs:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) apps/aos-tray/Sources/AOSTray/NativeInputDialog.swift:30— apps/aos-tray/Sources/AOSTray/NativeInputDialog.swift:30-34 | apps/aos-tray/Sources/AOSTray/PermissionDialog.swift:30-34 — 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 `apps/aos-tray/Sources/AOSTray/NativeInputDialog.swift:30` 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 (5 lines × 2) apps/adaptive-shell/src/fixtures.rs:1108— apps/adaptive-shell/src/fixtures.rs:1108-1112 | apps/adaptive-shell/src/fixtures.rs:1317-1321 — 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.
Hotspot: crates/unicity-aos-bootstrap/src/main.rs crates/unicity-aos-bootstrap/src/main.rs:334— crates/unicity-aos-bootstrap/src/main.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in unicity_aos_bootstrap::handle_product_command at line 334. 12 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 17:47:42 +04:00' --until='2026-10-21 17:47:42 +04:00' --full-history --no-merges -- crates/unicity-aos-bootstrap/src/main.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: crates/unicity-aos-bootstrap/src/mcp/mod.rs crates/unicity-aos-bootstrap/src/mcp/mod.rs:335— crates/unicity-aos-bootstrap/src/mcp/mod.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in unicity_aos_bootstrap::mcp::serve at line 335. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 17:47:42 +04:00' --until='2026-10-21 17:47:42 +04:00' --full-history --no-merges -- crates/unicity-aos-bootstrap/src/mcp/mod.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: crates/aos-mcp-broker/src/broker.rs crates/aos-mcp-broker/src/broker.rs:203— crates/aos-mcp-broker/src/broker.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in aos_mcp_broker::broker::handle_mcp_call at line 203. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 17:47:42 +04:00' --until='2026-10-21 17:47:42 +04:00' --full-history --no-merges -- crates/aos-mcp-broker/src/broker.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: crates/aos-mcp-broker/src/execute.rs crates/aos-mcp-broker/src/execute.rs:142— crates/aos-mcp-broker/src/execute.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in aos_mcp_broker::execute::dispatch_with_approval at line 142. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 17:47:42 +04:00' --until='2026-10-21 17:47:42 +04:00' --full-history --no-merges -- crates/aos-mcp-broker/src/execute.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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×4
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) capsules/capsule-surface-catalog/src/theme.rs:329— capsules/capsule-surface-catalog/src/theme.rs:329-341 | capsules/capsule-surface-catalog/src/theme.rs:377-387 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) capsules/capsule-react/src/lib.rs:193— capsules/capsule-react/src/lib.rs:193-203 | capsules/capsule-react/src/lib.rs:227-237 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) capsules/capsule-workspace-recipes/src/backend.rs:122— capsules/capsule-workspace-recipes/src/backend.rs:122-133 | capsules/capsule-workspace-recipes/src/backend.rs:153-163 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) scripts/check_glibc.py:53— scripts/check_glibc.py:53-64 | scripts/check_static_elf.py:78-88 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (12 lines × 2) apps/adaptive-shell/src/activity.rs:682— apps/adaptive-shell/src/activity.rs:682-693 | capsules/capsule-surface-model/src/store.rs:338-349 — before extracting anything, compare `apps/adaptive-shell/src/activity.rs` and `capsules/capsule-surface-model/src/store.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) apps/adaptive-shell/src/theme.rs:166— apps/adaptive-shell/src/theme.rs:166-177 | apps/adaptive-shell/src/theme.rs:190-201 — 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 `apps/adaptive-shell/src/theme.rs:166` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) crates/unicity-aos-bootstrap/src/mcp/interaction.rs:345— crates/unicity-aos-bootstrap/src/mcp/interaction.rs:345-356 | crates/unicity-aos-bootstrap/src/mcp/interaction.rs:429-440 — 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) capsules/capsule-openai-compat/src/lib.rs:55— capsules/capsule-openai-compat/src/lib.rs:55-66 | capsules/capsule-openai/src/lib.rs:55-66 — before extracting anything, compare `capsules/capsule-openai-compat/src/lib.rs` and `capsules/capsule-openai/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-openai-compat/src/lib.rs:55` 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.
OpenAICompatProvider::process_chunk (cognitive 32) capsules/capsule-openai-compat/src/lib.rs:461— OpenAICompatProvider::process_chunk has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 3 (7 pts), boolean chains 3 (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.
OpenAICompatProvider::parse_sse_stream_live (cognitive 19) capsules/capsule-openai-compat/src/lib.rs:378— OpenAICompatProvider::parse_sse_stream_live has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 2 (6 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.
OpenAICompatProvider::execute_request (cognitive 16) capsules/capsule-openai-compat/src/lib.rs:276— OpenAICompatProvider::execute_request has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenAIProvider::execute_request (cognitive 19) capsules/capsule-openai/src/lib.rs:199— OpenAIProvider::execute_request has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 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.
OpenAIProvider::handle_event (cognitive 18) capsules/capsule-openai/src/lib.rs:369— OpenAIProvider::handle_event has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, match/switch 1 (nesting depth added 7). 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.
OpenAIProvider::parse_sse_stream (cognitive 17) capsules/capsule-openai/src/lib.rs:322— OpenAIProvider::parse_sse_stream 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.
ClassTooLong: ReactLoop capsules/capsule-react/src/lib.rs:526— ClassTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 25 methods, 2 blocks, lines 529-2079. The bar is 400 significant lines; this is 244 over it, 1.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Store capsules/capsule-users/src/store.rs:79— ClassTooLong — 446 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 29 methods, 2 blocks, lines 79-699. The bar is 400 significant lines; this is 46 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: RecipeService capsules/capsule-workspace-recipes/src/service.rs:104— ClassTooLong — 438 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 2 blocks, lines 104-648. The bar is 400 significant lines; this is 38 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×3
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×3
Edited copy of a member (18 corresponding lines) apps/adaptive-shell/src/components.rs:867— apps/adaptive-shell/src/components.rs:867-886 | capsules/capsule-surface-model/src/components.rs:725-742 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) apps/adaptive-shell/src/activity.rs:101— apps/adaptive-shell/src/activity.rs:101-121 | apps/adaptive-shell/src/activity.rs:455-472 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) capsules/capsule-session/src/lib.rs:1123— capsules/capsule-session/src/lib.rs:1123-1140 | capsules/capsule-session/src/lib.rs:1183-1200 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×3
Edited copy of a member (12 corresponding lines) apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:330— apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:330-342 | apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:344-355 — 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) capsules/capsule-surface-model/src/recipe.rs:114— capsules/capsule-surface-model/src/recipe.rs:114-126 | apps/adaptive-shell/src/activity.rs:186-197 — 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) scripts/capsule_release.py:184— scripts/capsule_release.py:184-196 | scripts/validate-runtime-archive.py:18-29 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×3
Edited copy of a member (7 corresponding lines) crates/unicity-aos-bootstrap/src/command_center.rs:3— crates/unicity-aos-bootstrap/src/command_center.rs:3-12 | crates/unicity-aos-bootstrap/src/main.rs:561-567 — 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) crates/unicity-aos-bootstrap/src/lib.rs:662— crates/unicity-aos-bootstrap/src/lib.rs:662-668 | crates/unicity-aos-bootstrap/src/native_setup/mod.rs:674-680 — 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) apps/adaptive-shell/src/activity.rs:58— apps/adaptive-shell/src/activity.rs:58-64 | apps/adaptive-shell/src/atlas.rs:26-32 — 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 (9–10 lines × 2) capsules/capsule-openai-compat/src/lib.rs:359— capsules/capsule-openai-compat/src/lib.rs:359-367 | capsules/capsule-openai/src/lib.rs:300-309 — before extracting anything, compare `capsules/capsule-openai-compat/src/lib.rs` and `capsules/capsule-openai/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-openai-compat/src/lib.rs:359` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–10 lines × 2) capsules/capsule-users/src/responses.rs:37— capsules/capsule-users/src/responses.rs:37-46 | capsules/capsule-users/src/responses.rs:61-69 — 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 `capsules/capsule-users/src/responses.rs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `capsules/capsule-users/src/responses.rs:46` calls `insert`, `into`, `String` and `capsules/capsule-users/src/responses.rs:69` 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 (9–10 lines × 2) apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:118— apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:118-126 | apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift:68-77 — before extracting anything, compare `apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift` and `apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:118` 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.
Off the main sequence: aos-mcp-broker — aos-mcp-broker: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: AOSTrayCore — AOSTrayCore: abstractness 0.02, instability 0.00, distance 0.98 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: capsule-surface-model — capsule-surface-model: abstractness 0.06, instability 0.00, distance 0.94 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
ShellState::apply_with_context (cyclomatic 38) apps/adaptive-shell/src/input.rs:150— ShellState::apply_with_context has cyclomatic complexity 38 (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.
ShellState::apply_atlas_key (cyclomatic 16) apps/adaptive-shell/src/input.rs:281— ShellState::apply_atlas_key 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.
Patch::validate (cyclomatic 28) capsules/capsule-surface-model/src/store.rs:144— Patch::validate has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Patch::validate (cyclomatic 19) apps/adaptive-shell/src/activity.rs:551— Patch::validate has cyclomatic complexity 19 (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. This is NOT this file's highest cyclomatic complexity: PatchError::fmt (cyclomatic 20) 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 function is counted neither in this dimension's figures nor in its score.
PendingApprovals::upstream (cyclomatic 23) crates/unicity-aos-bootstrap/src/mcp/pending.rs:108— PendingApprovals::upstream 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.
PendingApprovals::downstream (cyclomatic 21) crates/unicity-aos-bootstrap/src/mcp/pending.rs:268— PendingApprovals::downstream 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.
OpenAIProvider::handle_event (cyclomatic 17) capsules/capsule-openai/src/lib.rs:369— OpenAIProvider::handle_event 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.
OpenAIProvider::execute_request (cyclomatic 16) capsules/capsule-openai/src/lib.rs:199— OpenAIProvider::execute_request has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
aos_mcp_broker::broker::handle_mcp_call (cyclomatic 17) crates/aos-mcp-broker/src/broker.rs:203— aos_mcp_broker::broker::handle_mcp_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.
aos_mcp_broker::execute::dispatch_with_approval (cyclomatic 17) crates/aos-mcp-broker/src/execute.rs:142— aos_mcp_broker::execute::dispatch_with_approval has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Repeated repair: crates/unicity-aos-bootstrap/src/lib.rs crates/unicity-aos-bootstrap/src/lib.rs:194— crates/unicity-aos-bootstrap/src/lib.rs changed 13 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is AosHome::ensure_unicity_ce_manifest at line 194), 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: preserve trusted distro upgrades with the Astrid RC6 pin (#246)”; “fix(runtime): select a consistent product daemon workspace (#224)”; “fix(init): grant the default fleet during first runtime init (#200)”; “fix(runtime): bound default musl compiler parallelism (#195)”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 17:47:42 +04:00' --until='2026-10-21 17:47:42 +04:00' --full-history --no-merges -- crates/unicity-aos-bootstrap/src/lib.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.
Repeated repair: crates/aos-mcp-broker/src/approval.rs crates/aos-mcp-broker/src/approval.rs:640— crates/aos-mcp-broker/src/approval.rs changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is aos_mcp_broker::approval::handle_mcp_ingress_respond at line 640), 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(mcp): surface nested provider delivery failures (#241)”; “fix(mcp): bind results to discovered providers (#174)”; “fix(approval): bind grants to pending requests (#171)”. 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-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 17:47:42 +04:00' --until='2026-10-21 17:47:42 +04:00' --full-history --no-merges -- crates/aos-mcp-broker/src/approval.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.
PendingApprovals::downstream (cognitive 37) crates/unicity-aos-bootstrap/src/mcp/pending.rs:268— PendingApprovals::downstream has cognitive complexity 37 (threshold 15). Drivers by points: if/else 18 (32 pts), loops 1 (3 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.
PendingApprovals::upstream (cognitive 32) crates/unicity-aos-bootstrap/src/mcp/pending.rs:108— PendingApprovals::upstream has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (27 pts), boolean chains 4, 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.
aos_hook_adapter_oracle::collect_additional_context (cognitive 32) capsules/capsule-hook-adapter-oracle/src/lib.rs:300— aos_hook_adapter_oracle::collect_additional_context has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 2 (6 pts), loops 2 (4 pts), boolean chains 3 (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.
aos_hook_adapter_oracle::collect_binding_response (cognitive 20) capsules/capsule-hook-adapter-oracle/src/lib.rs:462— aos_hook_adapter_oracle::collect_binding_response has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2 (3 pts), match/switch 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Patch::validate (cognitive 29) capsules/capsule-surface-model/src/store.rs:144— Patch::validate has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 8, match/switch 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Patch::validate (cognitive 20) apps/adaptive-shell/src/activity.rs:551— Patch::validate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 8, loops 2 (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.
ShellState::apply_with_context (cognitive 26) apps/adaptive-shell/src/input.rs:150— ShellState::apply_with_context has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 5, match/switch 2 (3 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ShellState::apply_atlas_key (cognitive 23) apps/adaptive-shell/src/input.rs:281— ShellState::apply_atlas_key has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2, match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
aos_prompt_builder::fire_before_prompt_build (cognitive 25) capsules/capsule-prompt-builder/src/lib.rs:337— aos_prompt_builder::fire_before_prompt_build has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (4 pts), match/switch 2 (3 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.
aos_prompt_builder::collect_tool_schemas (cognitive 23) capsules/capsule-prompt-builder/src/lib.rs:581— aos_prompt_builder::collect_tool_schemas has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (4 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodTooLong: ThemeTokens.resolve apps/adaptive-shell/src/theme.rs:144— MethodTooLong — resolve runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LayoutPolicy.resolve apps/adaptive-shell/src/layout.rs:115— MethodTooLong — resolve runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/unicity-aos-bootstrap/src/distro_trust.rs:266— crates/unicity-aos-bootstrap/src/distro_trust.rs:266-336 | crates/unicity-aos-bootstrap/src/migration.rs:331-414 | crates/unicity-aos-bootstrap/src/migration.rs:426-452 | crates/unicity-aos-bootstrap/src/migration.rs:778-806 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/unicity-aos-bootstrap/src/status/mounted_volume.rs:42— crates/unicity-aos-bootstrap/src/status/mounted_volume.rs:42-82 | crates/unicity-aos-bootstrap/src/updates/mod.rs:152-167 | crates/unicity-aos-bootstrap/src/updates/oracle.rs:28-86 | crates/unicity-aos-bootstrap/src/updates/process.rs:21-98 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) capsules/capsule-users/src/responses.rs:36— capsules/capsule-users/src/responses.rs:36-56 | capsules/capsule-users/src/responses.rs:60-74 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) apps/adaptive-shell/src/activity.rs:230— apps/adaptive-shell/src/activity.rs:230-244 | capsules/capsule-surface-model/src/recipe.rs:200-217 — 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 (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) capsules/capsule-users/src/store.rs:336— capsules/capsule-users/src/store.rs:336-361 | capsules/capsule-users/src/store.rs:531-554 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) capsules/capsule-session/src/lib.rs:539— capsules/capsule-session/src/lib.rs:539-562 | capsules/capsule-session/src/lib.rs:574-602 — 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 (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) apps/adaptive-shell/src/components.rs:556— apps/adaptive-shell/src/components.rs:556-584 | capsules/capsule-surface-model/src/components.rs:450-475 — 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.
Edited copy of a member (26 corresponding lines) crates/aos-mcp-broker/src/execute.rs:450— crates/aos-mcp-broker/src/execute.rs:450-475 | crates/aos-mcp-broker/src/execute.rs:563-591 — 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 (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) capsules/capsule-openai-compat/src/lib.rs:187— capsules/capsule-openai-compat/src/lib.rs:187-210 | capsules/capsule-openai/src/lib.rs:155-176 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) capsules/capsule-openai-compat/src/lib.rs:53— capsules/capsule-openai-compat/src/lib.rs:53-74 | capsules/capsule-openai/src/lib.rs:53-74 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) crates/unicity-aos-bootstrap/src/distro_trust.rs:503— crates/unicity-aos-bootstrap/src/distro_trust.rs:503-518 | crates/unicity-aos-bootstrap/src/distro_trust.rs:520-535 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/unicity-aos-bootstrap/src/migration.rs:945— crates/unicity-aos-bootstrap/src/migration.rs:945-961 | crates/unicity-aos-bootstrap/src/migration.rs:967-982 — 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 (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) capsules/capsule-identity/src/lib.rs:339— capsules/capsule-identity/src/lib.rs:339-352 | capsules/capsule-identity/src/lib.rs:354-367 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:163— apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:163-177 | apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:141-154 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) capsules/capsule-react/src/lib.rs:95— capsules/capsule-react/src/lib.rs:95-100 | capsules/capsule-session/src/lib.rs:117-122 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) capsules/capsule-cli/src/lib.rs:85— capsules/capsule-cli/src/lib.rs:85-90 | crates/unicity-aos-bootstrap/src/hook.rs:328-334 — 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 (22 lines × 2) capsules/capsule-rhai/src/lib.rs:389— capsules/capsule-rhai/src/lib.rs:389-410 | capsules/capsule-rhai/src/lib.rs:415-436 — 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 `capsules/capsule-rhai/src/lib.rs:389` 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 (22 lines × 2) apps/aos-tray/Sources/AOSTray/LibraryPrincipalForm.swift:24— apps/aos-tray/Sources/AOSTray/LibraryPrincipalForm.swift:24-45 | apps/aos-tray/Sources/AOSTray/NativeRuntimeSetupForm.swift:70-91 — 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 `apps/aos-tray/Sources/AOSTray/LibraryPrincipalForm.swift:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) capsules/capsule-openai-compat/src/lib.rs:384— capsules/capsule-openai-compat/src/lib.rs:384-401 | capsules/capsule-openai/src/lib.rs:326-342 — before extracting anything, compare `capsules/capsule-openai-compat/src/lib.rs` and `capsules/capsule-openai/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-openai-compat/src/lib.rs:384` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–18 lines × 2) apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:96— apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:96-112 | apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift:45-62 — before extracting anything, compare `apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift` and `apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:96` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (16 lines × 2) apps/adaptive-shell/src/activity.rs:531— apps/adaptive-shell/src/activity.rs:531-546 | capsules/capsule-surface-model/src/store.rs:91-106 — before extracting anything, compare `apps/adaptive-shell/src/activity.rs` and `capsules/capsule-surface-model/src/store.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:80— apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:80-95 | apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift:18-33 — before extracting anything, compare `apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift` and `apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 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 register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (15 lines × 2) capsules/capsule-workspace-recipes/src/service.rs:307— capsules/capsule-workspace-recipes/src/service.rs:307-321 | capsules/capsule-workspace-recipes/src/service.rs:394-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. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-workspace-recipes/src/service.rs:307` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:301— apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:301-315 | apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:187-201 — 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 `apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:301` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (13 lines × 2) capsules/capsule-openai-compat/src/lib.rs:218— capsules/capsule-openai-compat/src/lib.rs:218-230 | capsules/capsule-openai/src/lib.rs:184-196 — before extracting anything, compare `capsules/capsule-openai-compat/src/lib.rs` and `capsules/capsule-openai/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) capsules/capsule-users/src/store.rs:479— capsules/capsule-users/src/store.rs:479-491 | capsules/capsule-users/src/store.rs:670-682 — 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 `capsules/capsule-users/src/store.rs: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.
App::key (cyclomatic 32) crates/unicity-aos-bootstrap/src/console/mod.rs:155— App::key has cyclomatic complexity 32 (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.
StatusCommandReader.readBlocking (cyclomatic 30) apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift:15— StatusCommandReader.readBlocking 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.
NeutralFallback::token (cyclomatic 29) capsules/capsule-surface-catalog/src/theme.rs:446— NeutralFallback::token has cyclomatic complexity 29 (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.
LaunchArguments.parse (cyclomatic 28) apps/aos-tray/Sources/AOSTrayCore/Identity.swift:198— LaunchArguments.parse has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
capsule_surface_catalog::theme::validate_token (cyclomatic 26) capsules/capsule-surface-catalog/src/theme.rs:1079— capsule_surface_catalog::theme::validate_token has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NativeRuntimeSocket.open (cyclomatic 25) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSocket.swift:27— NativeRuntimeSocket.open 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.
PresentationCodec.parseRequest (cyclomatic 25) apps/aos-tray/Sources/AOSTrayCore/Protocol.swift:43— PresentationCodec.parseRequest has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ThemePack::validate (cyclomatic 24) capsules/capsule-surface-catalog/src/theme.rs:697— ThemePack::validate 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.
SocketEndpoint.validateBindPath (cyclomatic 24) apps/aos-tray/Sources/AOSTrayCore/SocketEndpoint.swift:14— SocketEndpoint.validateBindPath 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.
NativeInputRequest.validate (cyclomatic 22) apps/aos-tray/Sources/AOSTrayCore/NativeInput.swift:26— NativeInputRequest.validate 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.
Options::parse (cyclomatic 21) apps/adaptive-shell/src/main.rs:62— Options::parse has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
PrivateRuntimeFile.read (cyclomatic 20) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeConfiguration.swift:92— PrivateRuntimeFile.read 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.
PrincipalDiscoveryReader.readBlocking (cyclomatic 20) apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:79— PrincipalDiscoveryReader.readBlocking 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.
NativeRuntimeSetup.runBlocking (cyclomatic 19) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:156— NativeRuntimeSetup.runBlocking has cyclomatic complexity 19 (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.
ThemeTokens::resolve (cyclomatic 18) apps/adaptive-shell/src/theme.rs:144— ThemeTokens::resolve has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
OpenAICompatProvider::process_chunk (cyclomatic 17) capsules/capsule-openai-compat/src/lib.rs:461— OpenAICompatProvider::process_chunk 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.
RecipeService::open (cyclomatic 17) capsules/capsule-workspace-recipes/src/service.rs:111— RecipeService::open 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.
NativeRuntimeSocket.authenticate (cyclomatic 17) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeAuthentication.swift:7— NativeRuntimeSocket.authenticate has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
aos_forge::checks::check_tool_bus (cyclomatic 16) capsules/capsule-forge/src/checks.rs:222— aos_forge::checks::check_tool_bus 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.
aos_hook_adapter_oracle::collect_additional_context (cyclomatic 16) capsules/capsule-hook-adapter-oracle/src/lib.rs:300— aos_hook_adapter_oracle::collect_additional_context 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. This is NOT this file's highest cyclomatic complexity: aos_hook_adapter_oracle::claude_mapping (cyclomatic 27) 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 function is counted neither in this dimension's figures nor in its score.
ReactLoop::handle_llm_stream (cyclomatic 16) capsules/capsule-react/src/lib.rs:1002— ReactLoop::handle_llm_stream 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.
UnixPresentationServer.readFrame (cyclomatic 16) apps/aos-tray/Sources/AOSTrayCore/SocketListener.swift:256— UnixPresentationServer.readFrame has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TodoComment capsules/capsule-identity/src/lib.rs:177— // TODO: Move to a new capsule which handles env details. Time would be good too. — 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.
StatusCommandReader.readBlocking (cognitive 41) apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift:15— StatusCommandReader.readBlocking has cognitive complexity 41 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 7, ternaries 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.
LaunchArguments.parse (cognitive 40) apps/aos-tray/Sources/AOSTrayCore/Identity.swift:198— LaunchArguments.parse has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (27 pts), boolean chains 10, match/switch 1 (2 pts), loops 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.
RecipeService::open (cognitive 38) capsules/capsule-workspace-recipes/src/service.rs:111— RecipeService::open has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (24 pts), match/switch 2 (8 pts), boolean chains 3, 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.
UnixPresentationServer.readFrame (cognitive 37) apps/aos-tray/Sources/AOSTrayCore/SocketListener.swift:256— UnixPresentationServer.readFrame has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (36 pts), loops 1 (nesting depth added 22). Of this number, 36 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aos_forge::checks::check_tool_bus (cognitive 35) capsules/capsule-forge/src/checks.rs:222— aos_forge::checks::check_tool_bus has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (30 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 19). 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.
SocketEndpoint.validateBindPath (cognitive 35) apps/aos-tray/Sources/AOSTrayCore/SocketEndpoint.swift:14— SocketEndpoint.validateBindPath has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (29 pts), boolean chains 5, 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.
CliProxy::run (cognitive 34) capsules/capsule-cli/src/lib.rs:321— CliProxy::run has cognitive complexity 34 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 5 (9 pts), match/switch 3 (9 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.
NativeRuntimeSocket.open (cognitive 34) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSocket.swift:27— NativeRuntimeSocket.open has cognitive complexity 34 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 11, error handling 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ThemePack::validate (cognitive 32) capsules/capsule-surface-catalog/src/theme.rs:697— ThemePack::validate has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 6 (9 pts), boolean chains 6 (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.
capsule_surface_catalog::theme::validate_token (cognitive 32) capsules/capsule-surface-catalog/src/theme.rs:1079— capsule_surface_catalog::theme::validate_token has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 5, match/switch 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.
LayoutPolicy::resolve (cognitive 31) apps/adaptive-shell/src/layout.rs:115— LayoutPolicy::resolve has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (25 pts), loops 2 (5 pts), 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.
AtlasLayoutPolicy::resolve (cognitive 30) apps/adaptive-shell/src/atlas.rs:554— AtlasLayoutPolicy::resolve has cognitive complexity 30 (threshold 15). Drivers by points: if/else 20 (25 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
aos_hook_bridge::collect_responses (cognitive 28) capsules/capsule-hook-bridge/src/lib.rs:172— aos_hook_bridge::collect_responses has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 2 (6 pts), loops 2 (4 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.
PresentationCodec.parseRequest (cognitive 27) apps/aos-tray/Sources/AOSTrayCore/Protocol.swift:43— PresentationCodec.parseRequest has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 8, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PrivateRuntimeFile.read (cognitive 26) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeConfiguration.swift:92— PrivateRuntimeFile.read has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 7, loops 2, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PrincipalDiscoveryReader.readBlocking (cognitive 26) apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:79— PrincipalDiscoveryReader.readBlocking has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 5, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NativeInputRequest.validate (cognitive 25) apps/aos-tray/Sources/AOSTrayCore/NativeInput.swift:26— NativeInputRequest.validate has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 11, 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.
App::key (cognitive 23) crates/unicity-aos-bootstrap/src/console/mod.rs:155— App::key has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
aos_registry::dispatch_cli_run_messages (cognitive 22) capsules/capsule-registry/src/lib.rs:574— aos_registry::dispatch_cli_run_messages has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 1 (2 pts), boolean chains 1, 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.
aos_session::do_search (cognitive 22) capsules/capsule-session/src/lib.rs:746— aos_session::do_search has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (3 pts), match/switch 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.
CapsuleLibraryView.body (cognitive 22) apps/aos-tray/Sources/AOSTray/CapsuleLibraryView.swift:9— CapsuleLibraryView.body has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 1 (4 pts), match/switch 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.
NativeRuntimeSetup.runBlocking (cognitive 21) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:156— NativeRuntimeSetup.runBlocking has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 6, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
NativeRuntimeSocket.authenticate (cognitive 21) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeAuthentication.swift:7— NativeRuntimeSocket.authenticate has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 5 (10 pts), error handling 1 (nesting depth added 5). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
NeutralFallback::token (cognitive 20) capsules/capsule-surface-catalog/src/theme.rs:446— NeutralFallback::token has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (19 pts), match/switch 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.
RequiredReplies::parse (cognitive 19) capsules/capsule-hook-adapter-oracle/src/decision.rs:65— RequiredReplies::parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SystemTools::system_status (cognitive 19) capsules/capsule-system/src/lib.rs:235— SystemTools::system_status has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (8 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.
NativeRuntimeInputConnection.receive (cognitive 19) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeInputConnection.swift:84— NativeRuntimeInputConnection.receive has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Registry::run (cognitive 18) capsules/capsule-registry/src/lib.rs:745— Registry::run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 2, match/switch 1 (2 pts), 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.
NativeRuntimeSetup.realHome (cognitive 18) apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:256— NativeRuntimeSetup.realHome has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, 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.
capsule_surface_model::store::merge_disjoint_fields (cognitive 17) capsules/capsule-surface-model/src/store.rs:612— capsule_surface_model::store::merge_disjoint_fields has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (3 pts), match/switch 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.
OverviewView.body (cognitive 17) apps/aos-tray/Sources/AOSTray/OverviewView.swift:7— OverviewView.body has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 4, ternaries 2 (4 pts) (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.
aos_shell::check_single_command_catastrophic (cognitive 16) capsules/capsule-shell/src/lib.rs:265— aos_shell::check_single_command_catastrophic has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, loops 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.
Request::send (cognitive 16) crates/unicity-aos-bootstrap/src/console/model.rs:51— Request::send has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 3 (5 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
TooManyMethods: AosHome crates/unicity-aos-bootstrap/src/lib.rs:58— TooManyMethods — 41 methods, declared across 2 files: src/lib.rs (40), runtime_command/mod.rs (1). The bar is 30 methods; this is 11 over it, 1.37× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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.
Near-duplicate member pair (51 shared lines) capsules/capsule-workspace-recipes/src/service.rs:260— capsules/capsule-workspace-recipes/src/service.rs:260-321 | capsules/capsule-workspace-recipes/src/service.rs:328-408 — These two members are variants of one another: 51 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 (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:79— apps/aos-tray/Sources/AOSTrayCore/PrincipalDiscovery.swift:79-139 | apps/aos-tray/Sources/AOSTrayCore/StatusCommandReader.swift:15-90 — 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 (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:269— apps/aos-tray/Sources/AOSTrayCore/CommandCenterVolume.swift:269-328 | apps/aos-tray/Sources/AOSTrayCore/NativeRuntimeSetup.swift:156-219 — 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 (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) capsules/capsule-openai-compat/src/lib.rs:542— capsules/capsule-openai-compat/src/lib.rs:542-606 | capsules/capsule-openai/src/lib.rs:464-530 — 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 copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) apps/aos-tray/Sources/AOSTray/LibraryPrincipalForm.swift:24— apps/aos-tray/Sources/AOSTray/LibraryPrincipalForm.swift:24-58 | apps/aos-tray/Sources/AOSTray/NativeRuntimeSetupForm.swift:70-104 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) capsules/capsule-shell/src/lib.rs:509— capsules/capsule-shell/src/lib.rs:509-553 | capsules/capsule-shell/src/lib.rs:558-594 — 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 copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) capsules/capsule-users/src/lib.rs:112— capsules/capsule-users/src/lib.rs:112-143 | capsules/capsule-users/src/lib.rs:317-343 | capsules/capsule-users/src/lib.rs:391-420 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 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 (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) crates/unicity-aos-bootstrap/src/main.rs:257— crates/unicity-aos-bootstrap/src/main.rs:257-287 | crates/unicity-aos-bootstrap/src/main.rs:290-317 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) capsules/capsule-session/src/lib.rs:1088— capsules/capsule-session/src/lib.rs:1088-1115 | capsules/capsule-session/src/lib.rs:1210-1236 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) capsules/capsule-surface-model/src/activity.rs:37— capsules/capsule-surface-model/src/activity.rs:37-55 | capsules/capsule-surface-model/src/activity.rs:97-115 — 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 (6 members, 18+ corresponding lines) · ×1
Edited copies of one member (6 members, 18+ corresponding lines) capsules/capsule-users/src/lib.rs:146— capsules/capsule-users/src/lib.rs:146-170 | capsules/capsule-users/src/lib.rs:211-231 | capsules/capsule-users/src/lib.rs:234-254 | capsules/capsule-users/src/lib.rs:257-274 | capsules/capsule-users/src/lib.rs:277-294 | capsules/capsule-users/src/lib.rs:297-314 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) capsules/capsule-users/src/lib.rs:173— capsules/capsule-users/src/lib.rs:173-191 | capsules/capsule-users/src/lib.rs:346-366 | capsules/capsule-users/src/lib.rs:369-388 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) crates/unicity-aos-bootstrap/src/cli/principals.rs:31— crates/unicity-aos-bootstrap/src/cli/principals.rs:31-49 | crates/unicity-aos-bootstrap/src/cli/status.rs:36-54 | crates/unicity-aos-bootstrap/src/main.rs:899-915 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) apps/adaptive-shell/src/components.rs:382— apps/adaptive-shell/src/components.rs:382-394 | capsules/capsule-surface-model/src/components.rs:306-318 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) capsules/capsule-surface-model/src/activity.rs:22— capsules/capsule-surface-model/src/activity.rs:22-30 | capsules/capsule-surface-model/src/activity.rs:74-82 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) crates/aos-mcp-broker/src/cache.rs:235— crates/aos-mcp-broker/src/cache.rs:235-249 | crates/aos-mcp-broker/src/execute.rs:419-434 | crates/aos-mcp-broker/src/grant_decision.rs:241-255 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) crates/aos-mcp-broker/src/approval.rs:1102— crates/aos-mcp-broker/src/approval.rs:1102-1113 | crates/aos-mcp-broker/src/broker.rs:827-838 | crates/aos-mcp-broker/src/hook_gate.rs:158-169 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) crates/aos-mcp-broker/src/approval.rs:760— crates/aos-mcp-broker/src/approval.rs:760-772 | crates/aos-mcp-broker/src/approval.rs:978-990 | crates/aos-mcp-broker/src/approval.rs:994-1007 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 4+ corresponding lines) · ×1
Edited copies of one member (4 members, 4+ corresponding lines) apps/adaptive-shell/src/activity.rs:82— apps/adaptive-shell/src/activity.rs:82-85 | apps/adaptive-shell/src/atlas.rs:50-53 | apps/adaptive-shell/src/components.rs:591-594 | capsules/capsule-surface-model/src/error.rs:14-17 — These 4 members are one piece of code written 4 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) apps/adaptive-shell/src/components.rs:523— apps/adaptive-shell/src/components.rs:523-526 | capsules/capsule-surface-model/src/components.rs:422-425 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) capsules/capsule-openai-compat/src/lib.rs:609— capsules/capsule-openai-compat/src/lib.rs:609-616 | capsules/capsule-openai/src/lib.rs:533-540 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (78 lines × 2) apps/adaptive-shell/src/components.rs:623— apps/adaptive-shell/src/components.rs:623-700 | capsules/capsule-surface-model/src/components.rs:501-578 — before extracting anything, compare `apps/adaptive-shell/src/components.rs` and `capsules/capsule-surface-model/src/components.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (58 lines × 2) apps/adaptive-shell/src/components.rs:225— apps/adaptive-shell/src/components.rs:225-282 | capsules/capsule-surface-model/src/components.rs:149-206 — before extracting anything, compare `apps/adaptive-shell/src/components.rs` and `capsules/capsule-surface-model/src/components.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (41 lines × 2) apps/adaptive-shell/src/components.rs:747— apps/adaptive-shell/src/components.rs:747-787 | capsules/capsule-surface-model/src/components.rs:616-656 — before extracting anything, compare `apps/adaptive-shell/src/components.rs` and `capsules/capsule-surface-model/src/components.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (28 lines × 2) capsules/capsule-workspace-recipes/src/service.rs:278— capsules/capsule-workspace-recipes/src/service.rs:278-305 | capsules/capsule-workspace-recipes/src/service.rs:365-392 — 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 `capsules/capsule-workspace-recipes/src/service.rs:278` 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–20 lines × 2) capsules/capsule-openai-compat/src/lib.rs:191— capsules/capsule-openai-compat/src/lib.rs:191-210 | capsules/capsule-openai/src/lib.rs:158-176 — before extracting anything, compare `capsules/capsule-openai-compat/src/lib.rs` and `capsules/capsule-openai/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-openai-compat/src/lib.rs:191` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–19 lines × 2) capsules/capsule-react/src/lib.rs:848— capsules/capsule-react/src/lib.rs:848-866 | capsules/capsule-react/src/lib.rs:941-956 — 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 `capsules/capsule-react/src/lib.rs:848` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–19 lines × 2) capsules/capsule-shell/src/lib.rs:421— capsules/capsule-shell/src/lib.rs:421-439 | capsules/capsule-shell/src/lib.rs:470-486 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `args` to `RunShellArgs` in one and `SpawnBackgroundArgs` 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 (19 lines × 2) crates/unicity-aos-bootstrap/src/main.rs:258— crates/unicity-aos-bootstrap/src/main.rs:258-276 | crates/unicity-aos-bootstrap/src/main.rs:291-309 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 3) capsules/capsule-rhai/src/lib.rs:372— capsules/capsule-rhai/src/lib.rs:372-387 | capsules/capsule-rhai/src/lib.rs:398-413 | capsules/capsule-rhai/src/lib.rs:424-439 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-rhai/src/lib.rs:372` 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 × 8) capsules/capsule-surface-catalog/src/theme.rs:901— capsules/capsule-surface-catalog/src/theme.rs:901-915 | capsules/capsule-surface-catalog/src/theme.rs:921-935 | capsules/capsule-surface-catalog/src/theme.rs:941-955 | capsules/capsule-surface-catalog/src/theme.rs:960-974 | capsules/capsule-surface-catalog/src/theme.rs:980-994 | capsules/capsule-surface-catalog/src/theme.rs:1000-1014 | capsules/capsule-surface-catalog/src/theme.rs:1020-1034 | capsules/capsule-surface-catalog/src/theme.rs:1039-1053 — all 8 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 (38 lines × 2) apps/adaptive-shell/src/components.rs:801— apps/adaptive-shell/src/components.rs:801-838 | capsules/capsule-surface-model/src/components.rs:670-707 — before extracting anything, compare `apps/adaptive-shell/src/components.rs` and `capsules/capsule-surface-model/src/components.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 238 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12–14 lines × 2) capsules/capsule-openai-compat/src/lib.rs:543— capsules/capsule-openai-compat/src/lib.rs:543-554 | capsules/capsule-openai/src/lib.rs:465-478 — before extracting anything, compare `capsules/capsule-openai-compat/src/lib.rs` and `capsules/capsule-openai/src/lib.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 103 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-openai-compat/src/lib.rs:543` 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–11 lines × 2) capsules/capsule-users/src/store.rs:384— capsules/capsule-users/src/store.rs:384-394 | capsules/capsule-users/src/store.rs:443-452 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 3) capsules/capsule-users/src/lib.rs:334— capsules/capsule-users/src/lib.rs:334-343 | capsules/capsule-users/src/lib.rs:446-455 | capsules/capsule-users/src/lib.rs:494-502 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `capsules/capsule-users/src/lib.rs:334` 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 (5 lines × 4) crates/unicity-aos-bootstrap/src/distro_trust.rs:268— crates/unicity-aos-bootstrap/src/distro_trust.rs:268-272 | crates/unicity-aos-bootstrap/src/migration.rs:336-340 | crates/unicity-aos-bootstrap/src/migration.rs:428-432 | crates/unicity-aos-bootstrap/src/migration.rs:780-784 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) crates/unicity-aos-bootstrap/src/mcp/mod.rs:481— crates/unicity-aos-bootstrap/src/mcp/mod.rs:481-489 | crates/unicity-aos-bootstrap/src/mcp/mod.rs:571-581 | crates/unicity-aos-bootstrap/src/mcp/mod.rs:591-599 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/unicity-aos-bootstrap/src/mcp/mod.rs:481` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) crates/unicity-aos-bootstrap/src/migration.rs:347— crates/unicity-aos-bootstrap/src/migration.rs:347-354 | crates/unicity-aos-bootstrap/src/migration.rs:388-395 | crates/unicity-aos-bootstrap/src/migration.rs:708-715 — 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.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) scripts/musl_release_metadata.py:152— scripts/musl_release_metadata.py:152-183 | scripts/release_metadata.py:138-157 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
End-of-life runtime: Rust 1.95 rust-toolchain.toml:1— rust-toolchain.toml declares Rust 1.95 as this project's toolchain file, and Rust 1.95, superseded by 1.96 on 2026-05-28 (the Rust project patches only the current stable). An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-05-28 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Sync-over-async blocking apps/aos-tray/Sources/AOSTrayCore/UpdateInventory.swift:103— `run` is async and calls .waitUntilExit() — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
Duplicated predicate scripts/package_macos_command_center.py:25— `not member.is_file() or member.is_symlink()` appears character-identically in 2 files — scripts/package_macos_command_center.py, scripts/package_macos_filesystem.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 scripts/channel_transaction.py:31— `path.is_file() and not path.is_symlink()` appears character-identically in 4 files — scripts/channel_transaction.py, scripts/musl_release_metadata.py, scripts/nightly_version.py, scripts/release_metadata.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 scripts/capsule_release.py:344— `path.is_symlink() or not stat.S_ISREG(path.lstat().st_mode)` appears character-identically in 2 files — scripts/capsule_release.py, scripts/release_publication.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 scripts/channel_publication.py:38— `type(generation) is int and 0 < generation <= MAX_GENERATION` appears character-identically in 3 files — scripts/channel_publication.py, scripts/channel_transaction.py, scripts/release_metadata.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 scripts/musl_release_metadata.py:180— `type(item["size"]) is int and item["size"] > 0` appears character-identically in 2 files — scripts/musl_release_metadata.py, scripts/release_metadata.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 scripts/musl_release_metadata.py:54— `type(root["schema-version"]) is int and root["schema-version"] == 1` appears character-identically in 2 files — scripts/musl_release_metadata.py, scripts/release_metadata.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 crates/unicity-aos-bootstrap/src/updates/mod.rs:154— `!metadata.is_file() || metadata.file_type().is_symlink()` appears character-identically in 2 files — crates/unicity-aos-bootstrap/src/updates/mod.rs, crates/unicity-aos-bootstrap/src/updates/oracle.rs. 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 apps/adaptive-shell/src/activity.rs:24— `!value.is_empty() && value.len() <= maximum` appears character-identically in 2 files — apps/adaptive-shell/src/activity.rs, capsules/capsule-surface-model/src/recipe.rs. 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 crates/unicity-aos-bootstrap/src/command_center.rs:32— `metadata.file_type().is_symlink() || !metadata.is_dir()` appears character-identically in 7 files — crates/unicity-aos-bootstrap/src/command_center.rs, crates/unicity-aos-bootstrap/src/distro_trust.rs, crates/unicity-aos-bootstrap/src/legacy_private_permissions.rs, crates/unicity-aos-bootstrap/src/lib.rs. 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 crates/unicity-aos-bootstrap/src/distro_trust.rs:237— `metadata.file_type().is_symlink() || !metadata.is_file()` appears character-identically in 3 files — crates/unicity-aos-bootstrap/src/distro_trust.rs, crates/unicity-aos-bootstrap/src/lib.rs, crates/unicity-aos-bootstrap/src/migration.rs. 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 crates/unicity-aos-bootstrap/src/lib.rs:664— `metadata.is_file() && !metadata.file_type().is_symlink()` appears character-identically in 2 files — crates/unicity-aos-bootstrap/src/lib.rs, crates/unicity-aos-bootstrap/src/main.rs. 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 crates/unicity-aos-bootstrap/src/migration.rs:165— `path_metadata.file_type().is_symlink() || !path_metadata.is_file()` appears character-identically in 2 files — crates/unicity-aos-bootstrap/src/migration.rs, crates/unicity-aos-bootstrap/src/native_setup/mod.rs. 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 apps/adaptive-shell/src/activity.rs:685— `recipe.revision != patch.base_revision || recipe.digest != patch.base_digest` appears character-identically in 2 files — apps/adaptive-shell/src/activity.rs, capsules/capsule-surface-model/src/store.rs. 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 apps/adaptive-shell/src/activity.rs:571— `self.operations.is_empty() || self.operations.len() > MAX_PATCH_OPS` appears character-identically in 2 files — apps/adaptive-shell/src/activity.rs, capsules/capsule-surface-model/src/store.rs. 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 Err capsules/capsule-registry/src/lib.rs:251— `stamp_message_providers` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err capsules/capsule-system/src/lib.rs:195— `list_interfaces` turns every `Err` into `Ok("WIT directory not found. Run `aos init` to set up the standard interfaces.".into())` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
Silent fallback default on Err capsules/capsule-users/src/time.rs:29— `current_unix_millis` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
No ADRs found crates/unicity-aos-bootstrap/Cargo.toml:41— 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 `crates/unicity-aos-bootstrap/Cargo.toml` makes this repository a deployable product (line 41).
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 16/19 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/adaptive-shell`, `apps/aos-tray`, `crates/unicity-aos-bootstrap`.
Subsumed condition operand crates/unicity-aos-bootstrap/src/native_setup/mod.rs:455— `text.contains("unrecognized subcommand")` can never decide this `||` — every value satisfying `text.contains("unrecognized subcommand")` also satisfies `text.contains("unrecognized")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
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 apps/adaptive-shell/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p blake3` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.1 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.6"` requirement declared in crates/unicity-aos-bootstrap/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: objc2 — `objc2` 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 crates/unicity-aos-bootstrap/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p objc2` and commit the updated REDACTED.
Outdated: rhai — `rhai` is locked at 1.26.0 but 1.27.0 is the current stable release on crates.io, and it already satisfies the `"1.26.0"` requirement declared in capsules/capsule-rhai/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rhai` and commit the updated REDACTED.
Outdated: rustix — `rustix` is locked at 1.1.5 but 1.1.6 is the current stable release on crates.io, and it already satisfies the `"1.1"` requirement declared in crates/unicity-aos-bootstrap/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustix` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in apps/adaptive-shell/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` 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"` requirement declared in apps/adaptive-shell/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: 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"` requirement declared in crates/unicity-aos-bootstrap/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: uuid — `uuid` is locked at 1.25.0 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1.22"` requirement declared in capsules/capsule-memory/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` and commit the updated REDACTED.
Outdated: zeroize — `zeroize` is locked at 1.9.0 but 1.9.1 is the current stable release on crates.io, and it already satisfies the `"1.9"` requirement declared in crates/unicity-aos-bootstrap/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zeroize` and commit the updated REDACTED.
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.
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 01a1dafb-761f-7ee4-bffe-45877f65e69d · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Warnings: 298 · Recommendations: 23 · Info: 10 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 16:54 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.