Public report of AprilNEA/OpenLogi, published 27 October 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.10.5). 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, 27 October 2026, 00:35 UTC · Survey ID cd_9baeb7a2654044aab81c230abdf971c5
AprilNEA/OpenLogi
Measured 27 October 2026, 00:29 UTC, at code version 5f0435b
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreStrong
CriticalWeakAdequateStrongExemplary
Up 2 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 large codebase: 224,514 lines of product code in 21 projects, tests not counted · Estimated rebuild effort: about 2.6 person-years · Weakest lens: Production Readiness, 70
Findings by how serious they are
106 critical281 serious82 minor
11 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
27 October 2026, 00:29 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
63of 63 dimensions measured by tools.
428of 469 findings point to an exact file and line, so you can open each one in the code. The other 41 concern the repository as a whole, such as missing documentation.
63dimensions across 7 lenses, read from 224,514 lines of product code in 21 projects.
AprilNEA/OpenLogi meets our standard for a preview release. It scores 75 out of 100 and is rated Strong, and all 106 of its critical findings are security problems in the build pipeline.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is gathering the design records in one place, worth about 3 points. Fixing the set of other files with one main author comes next, worth about 1 point.
104 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One pipeline step puts outside input straight into a shell command, so an attacker can run commands in the build pipeline, and one secret can leak from the build pipeline. Pinning each tool to an exact version, passing outside input through environment variables and limiting the secret to its own step would close these risks.
The product code is 224,514 lines, about €380,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.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
Code composition: what the lines of code are
Product code 88%Tests 12%
New since the last survey: 132 findings
These 132 critical or serious findings weren't in the previous survey, on 13 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares 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: 28 findings
These 28 critical or serious findings were in the previous survey, on 13 October 2026, and are gone from this one.
€130,000 to €630,000, for 2,094 to 6,643 hours of work, about 2.6 person-years for 1 to 5 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 75. 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
Large: 224,514 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: Watchdog prices 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
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor.
Raises the score by about 1 point · Low effort · Bus Factor
3
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.
Raises the score by about 1 point · Low effort · Bus Factor
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
If you do one thing first · First action
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
565 modules, with 1549 dependencies between them. 11 loops run through 125 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 525 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.
openlogi_core.hid.route uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_core.hid.route, while a change to openlogi_core.hid.route can't break openlogi_core.device.
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.
11→14 openlogi_core.hid.smartshift uses openlogi_core.config.settingspart of a loop✕
Connections
1 pair of types, where a type in openlogi_core.hid.smartshift uses a type in openlogi_core.config.settings.
openlogi_core.hid.smartshift uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_core.hid.smartshift, while a change to openlogi_core.hid.smartshift can't break openlogi_core.config.settings.
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.
openlogi_hidpp.channel uses openlogi_hidpp.protocol.v10, so a change to openlogi_hidpp.protocol.v10 can break openlogi_hidpp.channel, while a change to openlogi_hidpp.channel can't break openlogi_hidpp.protocol.v10.
Position
Below the diagonal: openlogi_hidpp.channel uses a module listed above it, which is the healthy direction.
12→20 openlogi_hidpp.channel uses openlogi_hidpp.receiver.boltpart of a loop✕
Connections
1 pair of types, where a type in openlogi_hidpp.channel uses a type in openlogi_hidpp.receiver.bolt.
openlogi_hidpp.channel uses openlogi_hidpp.receiver.bolt, so a change to openlogi_hidpp.receiver.bolt can break openlogi_hidpp.channel, while a change to openlogi_hidpp.channel can't break openlogi_hidpp.receiver.bolt.
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.
openlogi_hook uses openlogi_core.app, so a change to openlogi_core.app can break openlogi_hook, while a change to openlogi_hook can't break openlogi_core.app.
Position
Below the diagonal: openlogi_hook uses a module listed above it, which is the healthy direction.
13→40 openlogi_hook uses openlogi_agent.lifecyclepart of a loop✕
Connections
3 pairs of types, where a type in openlogi_hook uses a type in openlogi_agent.lifecycle.
openlogi_hook uses openlogi_agent.lifecycle, so a change to openlogi_agent.lifecycle can break openlogi_hook, while a change to openlogi_hook can't break openlogi_agent.lifecycle.
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.
openlogi_core.config.settings uses openlogi_core.device.light, so a change to openlogi_core.device.light can break openlogi_core.config.settings, while a change to openlogi_core.config.settings can't break openlogi_core.device.light.
Position
Below the diagonal: openlogi_core.config.settings uses a module listed above it, which is the healthy direction.
openlogi_core.config.settings uses openlogi_core.hid.smartshift, so a change to openlogi_core.hid.smartshift can break openlogi_core.config.settings, while a change to openlogi_core.config.settings can't break openlogi_core.hid.smartshift.
Position
Below the diagonal: openlogi_core.config.settings uses a module listed above it, which is the healthy direction.
openlogi_core.device uses openlogi_core.device.light, so a change to openlogi_core.device.light can break openlogi_core.device, while a change to openlogi_core.device can't break openlogi_core.device.light.
Position
Below the diagonal: openlogi_core.device uses a module listed above it, which is the healthy direction.
openlogi_core.device uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_core.device, while a change to openlogi_core.device can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_core.device uses a module listed above it, which is the healthy direction.
openlogi_device.channel uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_device.channel, while a change to openlogi_device.channel can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_device.channel uses a module listed above it, which is the healthy direction.
openlogi_device.channel uses openlogi_hidpp.channel, so a change to openlogi_hidpp.channel can break openlogi_device.channel, while a change to openlogi_device.channel can't break openlogi_hidpp.channel.
Position
Below the diagonal: openlogi_device.channel uses a module listed above it, which is the healthy direction.
openlogi_core.config uses openlogi_core.binding.action, so a change to openlogi_core.binding.action can break openlogi_core.config, while a change to openlogi_core.config can't break openlogi_core.binding.action.
Position
Below the diagonal: openlogi_core.config uses a module listed above it, which is the healthy direction.
openlogi_core.config uses openlogi_core.binding.button, so a change to openlogi_core.binding.button can break openlogi_core.config, while a change to openlogi_core.config can't break openlogi_core.binding.button.
Position
Below the diagonal: openlogi_core.config uses a module listed above it, which is the healthy direction.
openlogi_core.config uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_core.config, while a change to openlogi_core.config can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_core.config uses a module listed above it, which is the healthy direction.
openlogi_core.config uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_core.config, while a change to openlogi_core.config can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_core.config uses a module listed above it, which is the healthy direction.
openlogi_core.config uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_core.config, while a change to openlogi_core.config can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_core.config uses a module listed above it, which is the healthy direction.
openlogi_core.config uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_core.config, while a change to openlogi_core.config can't break openlogi_core.device.
Position
Below the diagonal: openlogi_core.config uses a module listed above it, which is the healthy direction.
openlogi_core.hid.light uses openlogi_core.device.light, so a change to openlogi_core.device.light can break openlogi_core.hid.light, while a change to openlogi_core.hid.light can't break openlogi_core.device.light.
Position
Below the diagonal: openlogi_core.hid.light uses a module listed above it, which is the healthy direction.
openlogi_core.hid.light uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_core.hid.light, while a change to openlogi_core.hid.light can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_core.hid.light uses a module listed above it, which is the healthy direction.
openlogi_desktop.ui.theme uses openlogi_device.session.capture.redivert, so a change to openlogi_device.session.capture.redivert can break openlogi_desktop.ui.theme, while a change to openlogi_desktop.ui.theme can't break openlogi_device.session.capture.redivert.
Position
Below the diagonal: openlogi_desktop.ui.theme uses a module listed above it, which is the healthy direction.
openlogi_desktop.ui.theme uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_desktop.ui.theme, while a change to openlogi_desktop.ui.theme can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_desktop.ui.theme uses a module listed above it, which is the healthy direction.
openlogi_hidpp.receiver.bolt uses openlogi_hidpp.channel, so a change to openlogi_hidpp.channel can break openlogi_hidpp.receiver.bolt, while a change to openlogi_hidpp.receiver.bolt can't break openlogi_hidpp.channel.
Position
Below the diagonal: openlogi_hidpp.receiver.bolt uses a module listed above it, which is the healthy direction.
openlogi_hidpp.receiver.bolt uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_hidpp.receiver.bolt, while a change to openlogi_hidpp.receiver.bolt can't break openlogi_core.device.
Position
Below the diagonal: openlogi_hidpp.receiver.bolt uses a module listed above it, which is the healthy direction.
openlogi_desktop.state.devices uses openlogi_core.device.light, so a change to openlogi_core.device.light can break openlogi_desktop.state.devices, while a change to openlogi_desktop.state.devices can't break openlogi_core.device.light.
Position
Below the diagonal: openlogi_desktop.state.devices uses a module listed above it, which is the healthy direction.
openlogi_desktop.state.devices uses openlogi_desktop.state.device_key, so a change to openlogi_desktop.state.device_key can break openlogi_desktop.state.devices, while a change to openlogi_desktop.state.devices can't break openlogi_desktop.state.device_key.
Position
Below the diagonal: openlogi_desktop.state.devices uses a module listed above it, which is the healthy direction.
openlogi_desktop.state.devices uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_desktop.state.devices, while a change to openlogi_desktop.state.devices can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_desktop.state.devices uses a module listed above it, which is the healthy direction.
openlogi_desktop.state.devices uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_desktop.state.devices, while a change to openlogi_desktop.state.devices can't break openlogi_core.device.
Position
Below the diagonal: openlogi_desktop.state.devices uses a module listed above it, which is the healthy direction.
openlogi_desktop.state.devices uses openlogi_core.config, so a change to openlogi_core.config can break openlogi_desktop.state.devices, while a change to openlogi_desktop.state.devices can't break openlogi_core.config.
Position
Below the diagonal: openlogi_desktop.state.devices uses a module listed above it, which is the healthy direction.
openlogi_device.device_io uses openlogi_hidpp.receiver.bolt, so a change to openlogi_hidpp.receiver.bolt can break openlogi_device.device_io, while a change to openlogi_device.device_io can't break openlogi_hidpp.receiver.bolt.
Position
Below the diagonal: openlogi_device.device_io uses a module listed above it, which is the healthy direction.
openlogi_device.inventory.events uses openlogi_hidpp.protocol.v10, so a change to openlogi_hidpp.protocol.v10 can break openlogi_device.inventory.events, while a change to openlogi_device.inventory.events can't break openlogi_hidpp.protocol.v10.
Position
Below the diagonal: openlogi_device.inventory.events uses a module listed above it, which is the healthy direction.
openlogi_device.inventory.events uses openlogi_hidpp.channel, so a change to openlogi_hidpp.channel can break openlogi_device.inventory.events, while a change to openlogi_device.inventory.events can't break openlogi_hidpp.channel.
Position
Below the diagonal: openlogi_device.inventory.events uses a module listed above it, which is the healthy direction.
openlogi_device.inventory.events uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_device.inventory.events, while a change to openlogi_device.inventory.events can't break openlogi_core.device.
Position
Below the diagonal: openlogi_device.inventory.events uses a module listed above it, which is the healthy direction.
openlogi_device.inventory.events uses openlogi_hidpp.receiver.bolt, so a change to openlogi_hidpp.receiver.bolt can break openlogi_device.inventory.events, while a change to openlogi_device.inventory.events can't break openlogi_hidpp.receiver.bolt.
Position
Below the diagonal: openlogi_device.inventory.events uses a module listed above it, which is the healthy direction.
openlogi_hidpp.feature uses openlogi_hidpp.protocol.v10, so a change to openlogi_hidpp.protocol.v10 can break openlogi_hidpp.feature, while a change to openlogi_hidpp.feature can't break openlogi_hidpp.protocol.v10.
Position
Below the diagonal: openlogi_hidpp.feature uses a module listed above it, which is the healthy direction.
openlogi_hidpp.feature uses openlogi_hidpp.channel, so a change to openlogi_hidpp.channel can break openlogi_hidpp.feature, while a change to openlogi_hidpp.feature can't break openlogi_hidpp.channel.
Position
Below the diagonal: openlogi_hidpp.feature uses a module listed above it, which is the healthy direction.
openlogi_hidpp.feature uses openlogi_hidpp.receiver.bolt, so a change to openlogi_hidpp.receiver.bolt can break openlogi_hidpp.feature, while a change to openlogi_hidpp.feature can't break openlogi_hidpp.receiver.bolt.
Position
Below the diagonal: openlogi_hidpp.feature uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.app, so a change to openlogi_core.app can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.app.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.device.light, so a change to openlogi_core.device.light can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.device.light.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.hid.smartshift, so a change to openlogi_core.hid.smartshift can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.hid.smartshift.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.device.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_ipc.ipc uses openlogi_core.hid.light, so a change to openlogi_core.hid.light can break openlogi_ipc.ipc, while a change to openlogi_ipc.ipc can't break openlogi_core.hid.light.
Position
Below the diagonal: openlogi_ipc.ipc uses a module listed above it, which is the healthy direction.
openlogi_agent.bin.mock_agent uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_agent.bin.mock_agent, while a change to openlogi_agent.bin.mock_agent can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_agent.bin.mock_agent uses a module listed above it, which is the healthy direction.
openlogi_agent.bin.mock_agent uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_agent.bin.mock_agent, while a change to openlogi_agent.bin.mock_agent can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_agent.bin.mock_agent uses a module listed above it, which is the healthy direction.
openlogi_agent.bin.mock_agent uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_agent.bin.mock_agent, while a change to openlogi_agent.bin.mock_agent can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_agent.bin.mock_agent uses a module listed above it, which is the healthy direction.
openlogi_agent.bin.mock_agent uses openlogi_core.hid.smartshift, so a change to openlogi_core.hid.smartshift can break openlogi_agent.bin.mock_agent, while a change to openlogi_agent.bin.mock_agent can't break openlogi_core.hid.smartshift.
Position
Below the diagonal: openlogi_agent.bin.mock_agent uses a module listed above it, which is the healthy direction.
openlogi_agent.bin.mock_agent uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_agent.bin.mock_agent, while a change to openlogi_agent.bin.mock_agent can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_agent.bin.mock_agent uses a module listed above it, which is the healthy direction.
openlogi_agent.bin.mock_agent uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_agent.bin.mock_agent, while a change to openlogi_agent.bin.mock_agent can't break openlogi_core.device.
Position
Below the diagonal: openlogi_agent.bin.mock_agent uses a module listed above it, which is the healthy direction.
openlogi_agent.bin.mock_agent uses openlogi_core.hid.light, so a change to openlogi_core.hid.light can break openlogi_agent.bin.mock_agent, while a change to openlogi_agent.bin.mock_agent can't break openlogi_core.hid.light.
Position
Below the diagonal: openlogi_agent.bin.mock_agent uses a module listed above it, which is the healthy direction.
openlogi_agent.bin.mock_agent uses openlogi_ipc.ipc, so a change to openlogi_ipc.ipc can break openlogi_agent.bin.mock_agent, while a change to openlogi_agent.bin.mock_agent can't break openlogi_ipc.ipc.
Position
Below the diagonal: openlogi_agent.bin.mock_agent uses a module listed above it, which is the healthy direction.
openlogi_agent.virtual_keyboard uses openlogi_ipc.ipc, so a change to openlogi_ipc.ipc can break openlogi_agent.virtual_keyboard, while a change to openlogi_agent.virtual_keyboard can't break openlogi_ipc.ipc.
Position
Below the diagonal: openlogi_agent.virtual_keyboard uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware.context uses openlogi_core.device.light, so a change to openlogi_core.device.light can break openlogi_agent_core.hardware.context, while a change to openlogi_agent_core.hardware.context can't break openlogi_core.device.light.
Position
Below the diagonal: openlogi_agent_core.hardware.context uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware.context uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_agent_core.hardware.context, while a change to openlogi_agent_core.hardware.context can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_agent_core.hardware.context uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware.context uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_agent_core.hardware.context, while a change to openlogi_agent_core.hardware.context can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_agent_core.hardware.context uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware.context uses openlogi_core.hid.light, so a change to openlogi_core.hid.light can break openlogi_agent_core.hardware.context, while a change to openlogi_agent_core.hardware.context can't break openlogi_core.hid.light.
Position
Below the diagonal: openlogi_agent_core.hardware.context uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware.context uses openlogi_device.device_io, so a change to openlogi_device.device_io can break openlogi_agent_core.hardware.context, while a change to openlogi_agent_core.hardware.context can't break openlogi_device.device_io.
Position
Below the diagonal: openlogi_agent_core.hardware.context uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.ipc.request uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_desktop.services.ipc.request, while a change to openlogi_desktop.services.ipc.request can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_desktop.services.ipc.request uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.ipc.request uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_desktop.services.ipc.request, while a change to openlogi_desktop.services.ipc.request can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_desktop.services.ipc.request uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.ipc.request uses openlogi_desktop.state.device_key, so a change to openlogi_desktop.state.device_key can break openlogi_desktop.services.ipc.request, while a change to openlogi_desktop.services.ipc.request can't break openlogi_desktop.state.device_key.
Position
Below the diagonal: openlogi_desktop.services.ipc.request uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.ipc.request uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_desktop.services.ipc.request, while a change to openlogi_desktop.services.ipc.request can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_desktop.services.ipc.request uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.ipc.request uses openlogi_core.hid.smartshift, so a change to openlogi_core.hid.smartshift can break openlogi_desktop.services.ipc.request, while a change to openlogi_desktop.services.ipc.request can't break openlogi_core.hid.smartshift.
Position
Below the diagonal: openlogi_desktop.services.ipc.request uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.ipc.request uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_desktop.services.ipc.request, while a change to openlogi_desktop.services.ipc.request can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_desktop.services.ipc.request uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.ipc.request uses openlogi_core.hid.light, so a change to openlogi_core.hid.light can break openlogi_desktop.services.ipc.request, while a change to openlogi_desktop.services.ipc.request can't break openlogi_core.hid.light.
Position
Below the diagonal: openlogi_desktop.services.ipc.request uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.ipc.request uses openlogi_ipc.ipc, so a change to openlogi_ipc.ipc can break openlogi_desktop.services.ipc.request, while a change to openlogi_desktop.services.ipc.request can't break openlogi_ipc.ipc.
Position
Below the diagonal: openlogi_desktop.services.ipc.request uses a module listed above it, which is the healthy direction.
openlogi_device.backend uses openlogi_device.device_io, so a change to openlogi_device.device_io can break openlogi_device.backend, while a change to openlogi_device.backend can't break openlogi_device.device_io.
Position
Below the diagonal: openlogi_device.backend uses a module listed above it, which is the healthy direction.
openlogi_core.hid.error uses openlogi_device.backend, so a change to openlogi_device.backend can break openlogi_core.hid.error, while a change to openlogi_core.hid.error can't break openlogi_device.backend.
Position
Below the diagonal: openlogi_core.hid.error uses a module listed above it, which is the healthy direction.
31→33 openlogi_core.hid.error uses openlogi_agent_core.hardwarepart of a loop✕
Connections
1 pair of types, where a type in openlogi_core.hid.error uses a type in openlogi_agent_core.hardware.
openlogi_core.hid.error uses openlogi_agent_core.hardware, so a change to openlogi_agent_core.hardware can break openlogi_core.hid.error, while a change to openlogi_core.hid.error can't break openlogi_agent_core.hardware.
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.
openlogi_device.channel.registry uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_device.channel.registry, while a change to openlogi_device.channel.registry can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_device.channel.registry uses a module listed above it, which is the healthy direction.
openlogi_device.channel.registry uses openlogi_hidpp.channel, so a change to openlogi_hidpp.channel can break openlogi_device.channel.registry, while a change to openlogi_device.channel.registry can't break openlogi_hidpp.channel.
Position
Below the diagonal: openlogi_device.channel.registry uses a module listed above it, which is the healthy direction.
openlogi_device.channel.registry uses openlogi_device.channel, so a change to openlogi_device.channel can break openlogi_device.channel.registry, while a change to openlogi_device.channel.registry can't break openlogi_device.channel.
Position
Below the diagonal: openlogi_device.channel.registry uses a module listed above it, which is the healthy direction.
openlogi_device.channel.registry uses openlogi_hidpp.receiver.bolt, so a change to openlogi_hidpp.receiver.bolt can break openlogi_device.channel.registry, while a change to openlogi_device.channel.registry can't break openlogi_hidpp.receiver.bolt.
Position
Below the diagonal: openlogi_device.channel.registry uses a module listed above it, which is the healthy direction.
openlogi_device.channel.registry uses openlogi_device.backend, so a change to openlogi_device.backend can break openlogi_device.channel.registry, while a change to openlogi_device.channel.registry can't break openlogi_device.backend.
Position
Below the diagonal: openlogi_device.channel.registry uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_core.hid.smartshift, so a change to openlogi_core.hid.smartshift can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_core.hid.smartshift.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_device.channel, so a change to openlogi_device.channel can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_device.channel.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_device.device_io, so a change to openlogi_device.device_io can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_device.device_io.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_core.hid.error, so a change to openlogi_core.hid.error can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_core.hid.error.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_agent_core.hardware uses openlogi_device.channel.registry, so a change to openlogi_device.channel.registry can break openlogi_agent_core.hardware, while a change to openlogi_agent_core.hardware can't break openlogi_device.channel.registry.
Position
Below the diagonal: openlogi_agent_core.hardware uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.device_reads uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_desktop.services.device_reads, while a change to openlogi_desktop.services.device_reads can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_desktop.services.device_reads uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.device_reads uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_desktop.services.device_reads, while a change to openlogi_desktop.services.device_reads can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_desktop.services.device_reads uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.device_reads uses openlogi_desktop.state.device_key, so a change to openlogi_desktop.state.device_key can break openlogi_desktop.services.device_reads, while a change to openlogi_desktop.services.device_reads can't break openlogi_desktop.state.device_key.
Position
Below the diagonal: openlogi_desktop.services.device_reads uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.device_reads uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_desktop.services.device_reads, while a change to openlogi_desktop.services.device_reads can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_desktop.services.device_reads uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.device_reads uses openlogi_core.hid.smartshift, so a change to openlogi_core.hid.smartshift can break openlogi_desktop.services.device_reads, while a change to openlogi_desktop.services.device_reads can't break openlogi_core.hid.smartshift.
Position
Below the diagonal: openlogi_desktop.services.device_reads uses a module listed above it, which is the healthy direction.
openlogi_desktop.services.device_reads uses openlogi_core.hid.error, so a change to openlogi_core.hid.error can break openlogi_desktop.services.device_reads, while a change to openlogi_desktop.services.device_reads can't break openlogi_core.hid.error.
Position
Below the diagonal: openlogi_desktop.services.device_reads uses a module listed above it, which is the healthy direction.
openlogi_device.session.host_switch uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_device.session.host_switch, while a change to openlogi_device.session.host_switch can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_device.session.host_switch uses a module listed above it, which is the healthy direction.
openlogi_device.session.host_switch uses openlogi_hidpp.channel, so a change to openlogi_hidpp.channel can break openlogi_device.session.host_switch, while a change to openlogi_device.session.host_switch can't break openlogi_hidpp.channel.
Position
Below the diagonal: openlogi_device.session.host_switch uses a module listed above it, which is the healthy direction.
openlogi_device.session.host_switch uses openlogi_device.channel, so a change to openlogi_device.channel can break openlogi_device.session.host_switch, while a change to openlogi_device.session.host_switch can't break openlogi_device.channel.
Position
Below the diagonal: openlogi_device.session.host_switch uses a module listed above it, which is the healthy direction.
openlogi_device.session.host_switch uses openlogi_hidpp.receiver.bolt, so a change to openlogi_hidpp.receiver.bolt can break openlogi_device.session.host_switch, while a change to openlogi_device.session.host_switch can't break openlogi_hidpp.receiver.bolt.
Position
Below the diagonal: openlogi_device.session.host_switch uses a module listed above it, which is the healthy direction.
openlogi_device.session.host_switch uses openlogi_device.device_io, so a change to openlogi_device.device_io can break openlogi_device.session.host_switch, while a change to openlogi_device.session.host_switch can't break openlogi_device.device_io.
Position
Below the diagonal: openlogi_device.session.host_switch uses a module listed above it, which is the healthy direction.
openlogi_device.session.host_switch uses openlogi_agent.virtual_keyboard, so a change to openlogi_agent.virtual_keyboard can break openlogi_device.session.host_switch, while a change to openlogi_device.session.host_switch can't break openlogi_agent.virtual_keyboard.
Position
Below the diagonal: openlogi_device.session.host_switch uses a module listed above it, which is the healthy direction.
openlogi_device.session.host_switch uses openlogi_device.channel.registry, so a change to openlogi_device.channel.registry can break openlogi_device.session.host_switch, while a change to openlogi_device.session.host_switch can't break openlogi_device.channel.registry.
Position
Below the diagonal: openlogi_device.session.host_switch uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.app, so a change to openlogi_core.app can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.app.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.device.light, so a change to openlogi_core.device.light can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.device.light.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.device.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.config, so a change to openlogi_core.config can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.config.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_core.hid.light, so a change to openlogi_core.hid.light can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_core.hid.light.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_device.device_io, so a change to openlogi_device.device_io can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_device.device_io.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_ipc.ipc, so a change to openlogi_ipc.ipc can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_ipc.ipc.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_agent_core.hardware.context, so a change to openlogi_agent_core.hardware.context can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_agent_core.hardware.context.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_device.channel.registry, so a change to openlogi_device.channel.registry can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_device.channel.registry.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.orchestrator uses openlogi_agent_core.hardware, so a change to openlogi_agent_core.hardware can break openlogi_agent_core.orchestrator, while a change to openlogi_agent_core.orchestrator can't break openlogi_agent_core.hardware.
Position
Below the diagonal: openlogi_agent_core.orchestrator uses a module listed above it, which is the healthy direction.
openlogi_agent_core.watchers.gesture uses openlogi_hidpp.receiver.bolt, so a change to openlogi_hidpp.receiver.bolt can break openlogi_agent_core.watchers.gesture, while a change to openlogi_agent_core.watchers.gesture can't break openlogi_hidpp.receiver.bolt.
Position
Below the diagonal: openlogi_agent_core.watchers.gesture uses a module listed above it, which is the healthy direction.
openlogi_agent_core.watchers.gesture uses openlogi_device.channel.registry, so a change to openlogi_device.channel.registry can break openlogi_agent_core.watchers.gesture, while a change to openlogi_agent_core.watchers.gesture can't break openlogi_device.channel.registry.
Position
Below the diagonal: openlogi_agent_core.watchers.gesture uses a module listed above it, which is the healthy direction.
openlogi_agent_core.watchers.gesture uses openlogi_agent_core.hardware, so a change to openlogi_agent_core.hardware can break openlogi_agent_core.watchers.gesture, while a change to openlogi_agent_core.watchers.gesture can't break openlogi_agent_core.hardware.
Position
Below the diagonal: openlogi_agent_core.watchers.gesture uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.app, so a change to openlogi_core.app can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.app.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.binding.action, so a change to openlogi_core.binding.action can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.binding.action.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.binding.button, so a change to openlogi_core.binding.button can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.binding.button.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_desktop.state.device_key, so a change to openlogi_desktop.state.device_key can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_desktop.state.device_key.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.hid.smartshift, so a change to openlogi_core.hid.smartshift can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.hid.smartshift.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_hook, so a change to openlogi_hook can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_hook.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.config, so a change to openlogi_core.config can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.config.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_core.hid.light, so a change to openlogi_core.hid.light can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_core.hid.light.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_desktop.state.devices, so a change to openlogi_desktop.state.devices can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_desktop.state.devices.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_ipc.ipc, so a change to openlogi_ipc.ipc can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_ipc.ipc.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_desktop.services.ipc.request, so a change to openlogi_desktop.services.ipc.request can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_desktop.services.ipc.request.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_desktop.state uses openlogi_desktop.services.device_reads, so a change to openlogi_desktop.services.device_reads can break openlogi_desktop.state, while a change to openlogi_desktop.state can't break openlogi_desktop.services.device_reads.
Position
Below the diagonal: openlogi_desktop.state uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_core.hid.dpi, so a change to openlogi_core.hid.dpi can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_core.hid.dpi.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_core.hid.report_rate, so a change to openlogi_core.hid.report_rate can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_core.hid.report_rate.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_core.hid.route, so a change to openlogi_core.hid.route can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_core.hid.route.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_core.hid.smartshift, so a change to openlogi_core.hid.smartshift can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_core.hid.smartshift.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_core.config.settings, so a change to openlogi_core.config.settings can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_core.config.settings.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_core.device, so a change to openlogi_core.device can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_core.device.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_core.hid.light, so a change to openlogi_core.hid.light can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_core.hid.light.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_hidpp.receiver.bolt, so a change to openlogi_hidpp.receiver.bolt can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_hidpp.receiver.bolt.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_ipc.ipc, so a change to openlogi_ipc.ipc can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_ipc.ipc.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_core.hid.error, so a change to openlogi_core.hid.error can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_core.hid.error.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.server uses openlogi_agent_core.orchestrator, so a change to openlogi_agent_core.orchestrator can break openlogi_agent.server, while a change to openlogi_agent.server can't break openlogi_agent_core.orchestrator.
Position
Below the diagonal: openlogi_agent.server uses a module listed above it, which is the healthy direction.
openlogi_agent.lifecycle uses openlogi_hook, so a change to openlogi_hook can break openlogi_agent.lifecycle, while a change to openlogi_agent.lifecycle can't break openlogi_hook.
Position
Below the diagonal: openlogi_agent.lifecycle uses a module listed above it, which is the healthy direction.
openlogi_agent.lifecycle uses openlogi_core.config, so a change to openlogi_core.config can break openlogi_agent.lifecycle, while a change to openlogi_agent.lifecycle can't break openlogi_core.config.
Position
Below the diagonal: openlogi_agent.lifecycle uses a module listed above it, which is the healthy direction.
openlogi_agent.lifecycle uses openlogi_agent.virtual_keyboard, so a change to openlogi_agent.virtual_keyboard can break openlogi_agent.lifecycle, while a change to openlogi_agent.lifecycle can't break openlogi_agent.virtual_keyboard.
Position
Below the diagonal: openlogi_agent.lifecycle uses a module listed above it, which is the healthy direction.
openlogi_agent.lifecycle uses openlogi_agent_core.orchestrator, so a change to openlogi_agent_core.orchestrator can break openlogi_agent.lifecycle, while a change to openlogi_agent.lifecycle can't break openlogi_agent_core.orchestrator.
Position
Below the diagonal: openlogi_agent.lifecycle uses a module listed above it, which is the healthy direction.
openlogi_agent.lifecycle uses openlogi_agent.server, so a change to openlogi_agent.server can break openlogi_agent.lifecycle, while a change to openlogi_agent.lifecycle can't break openlogi_agent.server.
Position
Below the diagonal: openlogi_agent.lifecycle 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
A05:2025 — Injection
106
High / Critical
A03:2025 — Software Supply Chain Failures
20
Medium
Roadmap
First, organize architecture decision records under a dedicated docs folder with consistent naming to improve discoverability. Next, enable automated dependency review tools to strengthen security and performance, while updating the README to clearly explain how to run the test suite. Finally, address bus factor risks by resolving sole-ownership and off-boarding vulnerabilities to ensure knowledge distribution.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
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.
Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 102 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
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 — 106
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 — 281
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 — 82
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 11
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
Watchdog 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. 63 of 63 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 63 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, 428 of 469 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 — Watchdog 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: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 451 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. A hotspot's complexity is meant to be the worst body its churn actually touched. For crates/openlogi-desktop/src/services/ipc/request.rs, crates/openlogi-core/src/binding/action.rs that could not be established — the complexity reader for the file reports no body extents, or the history carries no per-line attribution — so the row quotes the file's worst body, which the counted changes may never have touched. The churn count is unaffected.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog 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. D21's deterministic naming 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. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Rust is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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.
X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 31 further occurrence(s) are not listed individually; the score already reflects all 71.
X5 Nullable reference types — not measured this run — Watchdog 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 Rust 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.
27 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was openlogi_core::config::identity::fold at 47. A further 23 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 Action::label at 56 — they are counted neither in the figure above nor in this dimension's score. 14 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: crates/openlogi-core/src/binding/action.rs (Action::label at 56), crates/openlogi-core/src/binding/action_ring/icon.rs (ActionRingIcon::asset_path at 54), crates/openlogi-core/src/binding/effect.rs (Action::effect at 49), crates/openlogi-desktop/src/features/binding_editor.rs (openlogi_desktop::features::binding_editor::action_icon_path at 44), crates/openlogi-inject/src/inject.rs (openlogi_inject::inject::hid_usage_to_windows at 31), and 9 more not listed here. 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.
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with openlogi_core::config::identity::fold (cyclomatic 47), openlogi_core::binding::key_combo::parse_key (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 2 together lifts Cyclomatic Complexity from 6.8 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
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.
+ 28 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 71 bodies over 15 down to 15 or less in Cognitive Complexity — start with openlogi_agent_core::watchers::foreground_app::spawn_native (cognitive 50), openlogi_device::pairing::drive (cognitive 44), openlogi_device::session::capture::monitor (cognitive 44). — 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 71 together lifts Cognitive Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.5 / 10Stronggated by 27 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 16 FileTooLong finding(s) in God Classes — start with devices.rs (2), orchestrator.rs, device_reads.rs. — One of this dimension's main actionable groups (16 warning-level).
Resolve the 4 TooManyMethods finding(s) in God Classes — start with state.rs, config.rs, orchestrator.rs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 ClassTooLong finding(s) in God Classes — start with device_reads.rs, orchestrator.rs, controls.rs. — One of this dimension's main actionable groups (4 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
59 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 2 of the 62 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.
+ 25 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with views.rs (2), function_row.rs, visual.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with profiles.rs, dpi.rs, haptic.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with server.rs, profile.rs, key_combo.rs. — One of this dimension's main actionable groups (5 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.3 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
21 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 7 module(s) off the main sequence, with abstractness counted on 18 of the 21 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: openlogi-assets · ×7
What to do
Resolve the 7 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (7 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with mock_agent.rs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
What to do
Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
3765 test methods: 3736 unit, 29 integration, 0 BDD, 0 e2e. The Rust suite contributes 3765 `#[test]` function(s) across 451 file(s) declaring at least one; its unit/integration split is Cargo's own — 2 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
25 outdated, 0 yanked direct Cargo dependencies. 94 of 99 direct crates were graded against crates.io (0 not published there, 5 not resolved by a committed REDACTED). 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: anyhow · ×25
What to do
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 998 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 5 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. 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/openlogi-desktop/src/features/binding_editor.rs (30×44=1320); crates/openlogi-desktop/src/app.rs (66×18=1188); crates/openlogi-agent/src/server.rs (50×18=900) Repeated repair below the complexity floor: crates/openlogi-hook/src/macos/watchdog.rs (8 of 8 changes were fixes); crates/openlogi-camera/src/capture_windows.rs (7 of 9 changes were fixes); crates/openlogi-device/src/thumbwheel.rs (6 of 8 changes were fixes)
Resolve the 41 Hotspot finding(s) in Churn × Complexity Hotspots — start with runtime.rs (2), pairing.rs (2), inventory.rs (2). — One of this dimension's main actionable groups (41 warning-level).
Resolve the 18 Repeated repair finding(s) in Churn × Complexity Hotspots — start with watchdog.rs, capture_windows.rs, thumbwheel.rs. — One of this dimension's main actionable groups (18 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor6.8 / 10Adequate✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
195 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/openlogi-desktop/src/services/device_reads.rs. Counted over 611 of the 723 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 224514 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.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question). How well each record argues its case is not measured.
4 of 20 build units (Cargo) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: 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).
106 finding(s): 0 critical, 106 high, 0 medium, 0 low. 102 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 13 file(s) — `crates/openlogi-agent/src/lifecycle.rs` (line 221, line 222, line 224), `crates/openlogi-camera/src/capture_macos.rs` (line 65, line 71, line 73, …), `crates/openlogi-desktop/src/features/camera/preview.rs` (line 172, line 197), `crates/openlogi-desktop/src/runtime.rs` (line 74), `crates/openlogi-desktop/src/state/camera.rs` (line 28), … (+8 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 102 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (104 issue-level, 2 of them charged here).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 9 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
Resolve the 3 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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 611 of the 723 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.
Resolve the 9 Change coupling finding(s) in Change Coupling — start with dpi.rs (2), editors.rs, binding_editor.rs. — One of this dimension's main actionable groups (9 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — 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 — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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. Scored 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. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 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.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
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 repo and its projects have a README, and whether it's substantive and current.
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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 18 of 21 project(s) that lack one — worth up to 1.7 pts.
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.
1 ADR-shaped document(s) detected by content — `docs/DECISIONS.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
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 model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability6.6 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 14/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/openlogi`, `xtask`.
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 the language 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.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
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 loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`info!` at line 213 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-overlay/src/ipc.rs:213
`debug!` at line 316 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-overlay/src/ipc.rs:316
`debug!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-overlay/src/platform/windows/native.rs:241
`warn!` at line 495 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:495
`warn!` at line 574 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:574
`warn!` at line 858 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:858
`warn!` at line 864 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:864
`warn!` at line 887 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:887
`warn!` at line 964 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:964
`warn!` at line 1002 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1002
`warn!` at line 1036 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1036
`warn!` at line 1041 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1041
`warn!` at line 1046 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1046
`warn!` at line 1058 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1058
`warn!` at line 1079 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1079
`debug!` at line 1118 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1118
`debug!` at line 1129 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1129
`warn!` at line 1135 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-inject/src/inject/linux.rs:1135
`error!` at line 133 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:133
`debug!` at line 163 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:163
`debug!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:185
`error!` at line 301 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:301
`warn!` at line 518 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:518
`debug!` at line 538 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:538
`error!` at line 551 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:551
`error!` at line 572 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:572
`debug!` at line 610 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux.rs:610
`error!` at line 157 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/macos.rs:157
`error!` at line 161 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/macos.rs:161
`debug!` at line 287 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/macos/translate.rs:287
`debug!` at line 148 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/foreground.rs:148
`debug!` at line 160 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/foreground.rs:160
`error!` at line 483 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/foreground.rs:483
`error!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/supervisor.rs:56
`error!` at line 178 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/supervisor.rs:178
`error!` at line 234 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/supervisor.rs:234
`info!` at line 282 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/supervisor.rs:282
`warn!` at line 284 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/supervisor.rs:284
`warn!` at line 347 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/supervisor.rs:347
`warn!` at line 364 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/openlogi-hook/src/linux/supervisor.rs:364
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 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.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; 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.
AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — 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
AX8 Test isolation — no test/production split to check
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~31847 lines of test source are present (.rs) 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.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
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 — Naming consistency is measured on C# only; JavaScript, Rust not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (openlogi-device), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 3 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 164 value object(s); 16 domain event(s); its domain events are published by services or handlers — no domain entity raises one; no aggregate is declared and no domain structure surrounds the state-guarding types: not claimed as DDD
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
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 — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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 applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
S1 Web-Security Posture — No web surface: 603 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
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.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
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.
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.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Hotspot: crates/openlogi-desktop/src/features/binding_editor.rs crates/openlogi-desktop/src/features/binding_editor.rs:60— crates/openlogi-desktop/src/features/binding_editor.rs changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in openlogi_desktop::features::binding_editor::action_icon_path at line 60. 1 of those changes was a fix/bug commit, and the other 29 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-desktop/src/features/binding_editor.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/openlogi-desktop/src/app.rs crates/openlogi-desktop/src/app.rs:330— crates/openlogi-desktop/src/app.rs changed 66 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AppView::repaints_for at line 330. 14 of those changes were fix/bug commits, and the other 52 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-desktop/src/app.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/openlogi-agent/src/server.rs crates/openlogi-agent/src/server.rs:893— crates/openlogi-agent/src/server.rs changed 50 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in RingHapticPlayer::spawn at line 893. 13 of those changes were fix/bug commits, and the other 37 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-agent/src/server.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/openlogi-desktop/src/services/ipc.rs crates/openlogi-desktop/src/services/ipc.rs:325— crates/openlogi-desktop/src/services/ipc.rs changed 53 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in openlogi_desktop::services::ipc::observe_loop at line 325. 11 of those changes were fix/bug commits, and the other 42 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-desktop/src/services/ipc.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/openlogi-overlay/src/main.rs crates/openlogi-overlay/src/main.rs:51— crates/openlogi-overlay/src/main.rs changed 36 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in openlogi_overlay::main at line 51. 8 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-overlay/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/openlogi-desktop/src/runtime.rs crates/openlogi-desktop/src/runtime.rs:286— crates/openlogi-desktop/src/runtime.rs changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Runtime::on_agent_update at line 286. 8 of those changes were fix/bug commits, and the other 25 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-desktop/src/runtime.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/openlogi-core/src/binding/action.rs crates/openlogi-core/src/binding/action.rs:354— crates/openlogi-core/src/binding/action.rs changed 10 times in last 90 days, max cyclomatic complexity 56 in Action::label at line 354. 2 of those changes were fix/bug commits, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-core/src/binding/action.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/openlogi-agent/src/lifecycle.rs crates/openlogi-agent/src/lifecycle.rs:402— crates/openlogi-agent/src/lifecycle.rs changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Running::apply_watcher at line 402. 16 of those changes were fix/bug commits, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-agent/src/lifecycle.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/openlogi-inject/src/inject/macos.rs crates/openlogi-inject/src/inject/macos.rs:231— crates/openlogi-inject/src/inject/macos.rs changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in openlogi_inject::inject::macos::combo at line 231. 11 of those changes were fix/bug commits, and the other 21 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-inject/src/inject/macos.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/openlogi-agent-core/src/watchers/keyboard.rs crates/openlogi-agent-core/src/watchers/keyboard.rs:255— crates/openlogi-agent-core/src/watchers/keyboard.rs changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in KeyboardManagerState::reconcile at line 255. 9 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-agent-core/src/watchers/keyboard.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/openlogi-device/src/pairing.rs crates/openlogi-device/src/pairing.rs:529— crates/openlogi-device/src/pairing.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in openlogi_device::pairing::drive at line 529. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-device/src/pairing.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/openlogi-agent-core/src/runtime.rs crates/openlogi-agent-core/src/runtime.rs:144— crates/openlogi-agent-core/src/runtime.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ActionExecutor::dispatch_to at line 144. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-agent-core/src/runtime.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/openlogi-desktop/src/services/ipc/request.rs crates/openlogi-desktop/src/services/ipc/request.rs:955— crates/openlogi-desktop/src/services/ipc/request.rs changed 14 times in last 90 days, max cyclomatic complexity 29 in Command::run at line 955. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-desktop/src/services/ipc/request.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/openlogi-desktop/src/state/inventory.rs crates/openlogi-desktop/src/state/inventory.rs:317— crates/openlogi-desktop/src/state/inventory.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AppState::adopt_transient_records at line 317. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-desktop/src/state/inventory.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/openlogi-agent-core/src/watchers/inventory.rs crates/openlogi-agent-core/src/watchers/inventory.rs:612— crates/openlogi-agent-core/src/watchers/inventory.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in InventoryWorker::next_trigger at line 612. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-agent-core/src/watchers/inventory.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/openlogi-device/src/inventory/events.rs crates/openlogi-device/src/inventory/events.rs:400— crates/openlogi-device/src/inventory/events.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in EventFeatureIndices::recognizes at line 400. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-device/src/inventory/events.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/openlogi-core/src/config/identity.rs crates/openlogi-core/src/config/identity.rs:247— crates/openlogi-core/src/config/identity.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in openlogi_core::config::identity::fold at line 247. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-core/src/config/identity.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/openlogi-inject/src/inject/linux.rs crates/openlogi-inject/src/inject/linux.rs:78— crates/openlogi-inject/src/inject/linux.rs changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in openlogi_inject::inject::linux::combo at line 78. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-inject/src/inject/linux.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/openlogi-device/src/inventory/features.rs crates/openlogi-device/src/inventory/features.rs:492— crates/openlogi-device/src/inventory/features.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in openlogi_device::inventory::features::probe_extra_capabilities at line 492. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-device/src/inventory/features.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/openlogi-hook/src/linux.rs crates/openlogi-hook/src/linux.rs:506— crates/openlogi-hook/src/linux.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in openlogi_hook::linux::device_thread at line 506. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hook/src/linux.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/openlogi-desktop/src/features/camera/controls.rs crates/openlogi-desktop/src/features/camera/controls.rs:195— crates/openlogi-desktop/src/features/camera/controls.rs changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in CameraControlsPanel::ensure_built at line 195. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-desktop/src/features/camera/controls.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/openlogi-device/src/channel/route.rs crates/openlogi-device/src/channel/route.rs:44— crates/openlogi-device/src/channel/route.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in openlogi_device::channel::route::open_route_channel at line 44. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-device/src/channel/route.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/openlogi-core/src/binding/key_combo.rs crates/openlogi-core/src/binding/key_combo.rs:61— crates/openlogi-core/src/binding/key_combo.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in KeyboardUsage::label at line 61. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-core/src/binding/key_combo.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/openlogi-device/src/inventory/cache.rs crates/openlogi-device/src/inventory/cache.rs:197— crates/openlogi-device/src/inventory/cache.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in openlogi_device::inventory::cache::probe_or_reuse_registered at line 197. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-device/src/inventory/cache.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: xtask/src/commands/ci/jobs/steps.rs xtask/src/commands/ci/jobs/steps.rs:138— xtask/src/commands/ci/jobs/steps.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in xtask::commands::ci::jobs::steps::plan at line 138. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- xtask/src/commands/ci/jobs/steps.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/openlogi-hook/src/macos/watchdog.rs crates/openlogi-hook/src/macos/watchdog.rs:266— crates/openlogi-hook/src/macos/watchdog.rs changed 8 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is LifecycleWatchdog::evaluate at line 266), 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(hook): restore the short watchdog budget before tap teardown (#1600)”; “fix(hook): charge the callback watchdog's first poll from its spawn”; “fix(hook): give the callback watchdog the same watched-time rule”; “fix(hook): discount only the watchdog gaps that spanned a kernel sleep or wake”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hook/src/macos/watchdog.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/openlogi-camera/src/capture_windows.rs crates/openlogi-camera/src/capture_windows.rs:489— crates/openlogi-camera/src/capture_windows.rs changed 9 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is openlogi_camera::capture_windows::activate_source at line 489), 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(camera): require a stored frame before reporting startup”; “fix(camera): refuse a camera another application is streaming”; “fix: resolve remaining state-machine audit findings (#1083)”; “fix(camera): finish the 1.98 chunks_exact sweep in the platform backends”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-camera/src/capture_windows.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/openlogi-device/src/thumbwheel.rs crates/openlogi-device/src/thumbwheel.rs:95— crates/openlogi-device/src/thumbwheel.rs changed 8 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is RotationStatus::from_byte at line 95), 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(device): restore thumb-wheel reporting as found and harden its capture (#1935)”; “fix(device): end a thumb-wheel roll whose Stop never arrives (#1777)”; “fix(hidpp): preserve device state OpenLogi does not own on writes (#1753)”; “fix(hid): normalize thumbwheel direction per device (#1158)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-device/src/thumbwheel.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/openlogi-core/src/config/file.rs crates/openlogi-core/src/config/file.rs:311— crates/openlogi-core/src/config/file.rs changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is openlogi_core::config::file::parse_config at line 311), 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(core): preserve symlinked configuration targets (#1642)”; “fix(core): serialize configuration saves across processes”; “fix(hid): normalize thumbwheel direction per device (#1158)”; “fix: resolve remaining state-machine audit findings (#1083)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-core/src/config/file.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/openlogi-device/src/inventory/probe/bolt.rs crates/openlogi-device/src/inventory/probe/bolt.rs:114— crates/openlogi-device/src/inventory/probe/bolt.rs changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is openlogi_device::inventory::probe::bolt::assemble_bolt_probe at line 114), 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(device): bound Bolt receiver identity reads (#2009)”; “fix(hid): read whole Bolt slot names, from 0x0005 or both codename chunks (#1962)”; “fix(hid): suppress duplicate Bolt pairing slots (#963)”; “fix(device): re-read settings the device changes itself (#1791)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-device/src/inventory/probe/bolt.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/openlogi-hidpp/src/feature/extended_dpi.rs crates/openlogi-hidpp/src/feature/extended_dpi.rs:126— crates/openlogi-hidpp/src/feature/extended_dpi.rs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is ExtendedDpiFeature::get_sensor_dpi_ranges at line 126), 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(hidpp,device): reconcile DPI after a sensor calibration broadcast (#1947)”; “fix(device): re-read settings the device changes itself (#1791)”; “fix(hidpp): require the sensor echo in DPI replies (#1776)”; “fix(device): write SmartShift torque and DPI only as the device advertises (#1759)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hidpp/src/feature/extended_dpi.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/openlogi-hidpp/src/receiver/bolt/event.rs crates/openlogi-hidpp/src/receiver/bolt/event.rs:59— crates/openlogi-hidpp/src/receiver/bolt/event.rs changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is openlogi_hidpp::receiver::bolt::event::decode at line 59), 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(hidpp): treat a Bolt protocol byte in 0x41 as an encrypted link (#1784)”; “fix(hidpp): preserve device state OpenLogi does not own on writes (#1753)”; “fix: resolve remaining state-machine audit findings (#1083)”; “fix(hidpp): read Unifying link encryption from bit 5, not the software-present bit (#924)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hidpp/src/receiver/bolt/event.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/openlogi-hidpp/src/feature/haptic_feedback.rs crates/openlogi-hidpp/src/feature/haptic_feedback.rs:73— crates/openlogi-hidpp/src/feature/haptic_feedback.rs changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is HapticIntensity::new at line 73), 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(device): refuse haptic plays while 0x19b0 reports a non-zero status (#1817)”; “fix(device): play only the haptic waveforms the device advertises (#1796)”; “fix(device): confirm the haptic repair from the device's reply (#1773)”; “fix(hidpp): preserve device state OpenLogi does not own on writes (#1753)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hidpp/src/feature/haptic_feedback.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/openlogi-inject/src/inject/macos/scroll.rs crates/openlogi-inject/src/inject/macos/scroll.rs:90— crates/openlogi-inject/src/inject/macos/scroll.rs changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is openlogi_inject::inject::macos::scroll::post_continuous_scroll at line 90), 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(macos): carry integer wheel ticks on synthetic line scroll events (#1969)”; “fix(macos): preserve fractional wheel distance (#1154)”; “fix(scroll): post phaseless continuous scroll events on macOS (#1157)”; “fix(macos): preserve pixel precision in synthetic scroll events (#1156)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-inject/src/inject/macos/scroll.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/openlogi-hidpp/src/protocol/v20.rs crates/openlogi-hidpp/src/protocol/v20.rs:204— crates/openlogi-hidpp/src/protocol/v20.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is HidppChannel::send_v20_write_through at line 204), 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(device): drop short 0x2121 movements and re-read SmartShift on a ratchet switch (#1944)”; “fix(device): stop committing 0x8080 frames the keyboard rejected (#1764)”; “fix(hidpp): quarantine an abandoned request's reply even for a byte-identical re-ask”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hidpp/src/protocol/v20.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/openlogi-overlay/src/session.rs crates/openlogi-overlay/src/session.rs:99— crates/openlogi-overlay/src/session.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is openlogi_overlay::session::spawn_click_away_dismissal at line 99), 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(linux): open the Actions Ring at the cursor on Wayland (#1004)”; “fix: resolve remaining state-machine audit findings (#1083)”; “fix(overlay,agent): stop the anonymous overlay tenant from wedging the Actions Ring (#848)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-overlay/src/session.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/openlogi-hidpp/src/feature/device_friendly_name.rs crates/openlogi-hidpp/src/feature/device_friendly_name.rs:164— crates/openlogi-hidpp/src/feature/device_friendly_name.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is DeviceFriendlyNameFeature::set_whole_device_name at line 164), 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(hidpp): check the echoed index in 0x8070/0x8071 info and 0x0007 name reads (#1789)”; “fix(hidpp): write each 0x0007 name chunk at its own offset (#1767)”; “fix: satisfy the lints Rust 1.98 added”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hidpp/src/feature/device_friendly_name.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/openlogi-overlay/src/platform/windows/native.rs crates/openlogi-overlay/src/platform/windows/native.rs:81— crates/openlogi-overlay/src/platform/windows/native.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is openlogi_overlay::platform::windows::native::sample_monitor at line 81), 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(overlay): keep the Windows Actions Ring from taking the foreground (#2053)”; “fix(overlay): draw the Windows Actions Ring without a window frame (#1913)”; “fix(overlay): properly position and scale Actions Ring on Windows mixed-DPI displays (#1745)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-overlay/src/platform/windows/native.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/openlogi-hidpp/src/feature/battery_status.rs crates/openlogi-hidpp/src/feature/battery_status.rs:124— crates/openlogi-hidpp/src/feature/battery_status.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is LegacyBatteryCapability::reports_mileage at line 124), 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(device): read the 0x1000 battery capability before mapping levels (#1938)”; “fix(device): reconcile inventory on 0x1000/0x1001 battery broadcasts (#1787)”; “fix(device): stop misreading 0x1000 and 0x1001 battery states (#1768)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hidpp/src/feature/battery_status.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/openlogi-hidpp/src/feature/illumination.rs crates/openlogi-hidpp/src/feature/illumination.rs:127— crates/openlogi-hidpp/src/feature/illumination.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is IlluminationFeature::get_brightness_effective_max at line 127), 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(hidpp): gate the illumination effective maximum in its wrapper (#1937)”; “fix(hidpp): refuse short 0x1990 info and level replies (#1772)”; “fix(hidpp): write 0x1990 non-linear level tables whole (#1765)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hidpp/src/feature/illumination.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/openlogi-hidpp/src/feature/illumination/types.rs crates/openlogi-hidpp/src/feature/illumination/types.rs:166— crates/openlogi-hidpp/src/feature/illumination/types.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is SetLevels::to_payloads at line 166), 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(hidpp): gate the illumination effective maximum in its wrapper (#1937)”; “fix(hidpp): write 0x1990 non-linear level tables whole (#1765)”; “fix(hidpp): keep events when a field carries an unknown enum value (#432)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-hidpp/src/feature/illumination/types.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/openlogi-desktop/src/windows.rs crates/openlogi-desktop/src/windows.rs:130— crates/openlogi-desktop/src/windows.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is openlogi_desktop::windows::open_or_focus at line 130), 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(gui): draw the client-side titlebar only where the compositor declines one (#945)”; “fix(gui): survive and complete the live language switch (#1033)”; “fix(gui): give the auxiliary windows the app's real Wayland identity”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-desktop/src/windows.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/openlogi-inject/src/inject/macos/symbolic_hotkey.rs crates/openlogi-inject/src/inject/macos/symbolic_hotkey.rs:134— crates/openlogi-inject/src/inject/macos/symbolic_hotkey.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 8 (its worst body is openlogi_inject::inject::macos::symbolic_hotkey::keystroke at line 134), 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(macos): switch Spaces through the user's shortcut so the Dock slides (#1847)”; “fix(macos): confirm desktop switches with private space APIs (#1586)”; “fix(macos): press shortcut keys where the active layout types them (#948)”. 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-29..2026-10-27, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-29 04:58:53 +08:00' --until='2026-10-27 04:58:53 +08:00' --full-history --no-merges -- crates/openlogi-inject/src/inject/macos/symbolic_hotkey.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.
FileTooLong: src/orchestrator.rs crates/openlogi-agent-core/src/orchestrator.rs— FileTooLong — 1176 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 71% of them inside a single declaration: Orchestrator (2 blocks, 513-2035). The bar is 500 significant lines; this is 676 over it, 2.35× 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: services/device_reads.rs crates/openlogi-desktop/src/services/device_reads.rs— FileTooLong — 1008 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: DeviceReads (2 blocks, 66-1504). The bar is 500 significant lines; this is 508 over it, 2.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: bin/mock_agent.rs crates/openlogi-agent/src/bin/mock_agent.rs— FileTooLong — 970 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 470 over it, 1.94× 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/hardware.rs crates/openlogi-agent-core/src/hardware.rs— FileTooLong — 820 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 320 over it, 1.64× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: session/host_switch.rs crates/openlogi-device/src/session/host_switch.rs— FileTooLong — 770 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 31 free functions. The bar is 500 significant lines; this is 270 over it, 1.54× 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: mouse/inspector.rs crates/openlogi-desktop/src/features/mouse/inspector.rs— FileTooLong — 738 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 238 over it, 1.48× 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: app/detail.rs crates/openlogi-desktop/src/app/detail.rs— FileTooLong — 734 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 234 over it, 1.47× 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: inject/linux.rs crates/openlogi-inject/src/inject/linux.rs— FileTooLong — 696 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 58 free functions. The bar is 500 significant lines; this is 196 over it, 1.39× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: keyboard/function_row.rs crates/openlogi-desktop/src/features/keyboard/function_row.rs— FileTooLong — 690 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 190 over it, 1.38× 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/server.rs crates/openlogi-agent/src/server.rs— FileTooLong — 656 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 156 over it, 1.31× 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: mouse/view.rs crates/openlogi-desktop/src/features/mouse/view.rs— FileTooLong — 622 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 122 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: state/devices.rs crates/openlogi-desktop/src/state/devices.rs— FileTooLong — 569 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 69 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: app/home.rs crates/openlogi-desktop/src/app/home.rs— FileTooLong — 548 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 48 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ipc/request.rs crates/openlogi-desktop/src/services/ipc/request.rs— FileTooLong — 547 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 47 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: orchestrator/devices.rs crates/openlogi-agent-core/src/orchestrator/devices.rs— FileTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 32 free functions. The bar is 500 significant lines; this is 34 over it, 1.07× 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: state/light.rs crates/openlogi-desktop/src/state/light.rs— FileTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 81% of them inside a single declaration: AppState (97-705). The bar is 500 significant lines; this is 24 over it, 1.05× 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.
openlogi_device::pairing::drive (cognitive 44) crates/openlogi-device/src/pairing.rs:529— openlogi_device::pairing::drive has cognitive complexity 44 (threshold 15). Drivers by points: if/else 9 (31 pts), match/switch 4 (12 pts), loops 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_device::session::capture::monitor (cognitive 44) crates/openlogi-device/src/session/capture.rs:351— openlogi_device::session::capture::monitor has cognitive complexity 44 (threshold 15). Drivers by points: if/else 11 (33 pts), match/switch 4 (10 pts), loops 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_device::session::gesture::arm::arm_controls_into (cognitive 37) crates/openlogi-device/src/session/gesture/arm.rs:201— openlogi_device::session::gesture::arm::arm_controls_into has cognitive complexity 37 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 8, loops 4 (8 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_device::channel::route::open_route_channel (cognitive 30) crates/openlogi-device/src/channel/route.rs:44— openlogi_device::channel::route::open_route_channel has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_device::inventory::cache::probe_or_reuse_registered (cognitive 30) crates/openlogi-device/src/inventory/cache.rs:197— openlogi_device::inventory::cache::probe_or_reuse_registered has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (21 pts), match/switch 3 (6 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
openlogi_device::session::host_switch::watch_host_switch (cognitive 28) crates/openlogi-device/src/session/host_switch.rs:677— openlogi_device::session::host_switch::watch_host_switch has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (22 pts), match/switch 2 (5 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.
openlogi_device::pairing::open_receiver_with_inventory (cognitive 21) crates/openlogi-device/src/pairing.rs:321— openlogi_device::pairing::open_receiver_with_inventory has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 5, match/switch 2 (4 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.
openlogi_device::inventory::features::probe_features (cognitive 17) crates/openlogi-device/src/inventory/features.rs:291— openlogi_device::inventory::features::probe_features has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 5 (9 pts), if/else 4 (7 pts), boolean chains 1 (nesting depth added 7). 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.
openlogi_device::inventory::features::probe_extra_capabilities (cognitive 16) crates/openlogi-device/src/inventory/features.rs:492— openlogi_device::inventory::features::probe_extra_capabilities has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 2). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_device::inventory::probe::bolt::assemble_bolt_probe (cognitive 16) crates/openlogi-device/src/inventory/probe/bolt.rs:114— openlogi_device::inventory::probe::bolt::assemble_bolt_probe has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×9
Change coupling: editors.rs ↔ inspector.rs crates/openlogi-desktop/src/features/keyboard/editors.rs:1— `crates/openlogi-desktop/src/features/keyboard/editors.rs` and `crates/openlogi-desktop/src/features/mouse/inspector.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `6fa7e50f` fix(gui): give MenuRow-based list rows an accessible name (#1448); `46a8a011` refactor(gui): import the binding-editor chrome from where it lives; `8d70a471` refactor(gui): let binding mutators report BindingsChanged themselves — run `git show` on any of them.
Change coupling: binding_editor.rs ↔ view.rs crates/openlogi-desktop/src/features/binding_editor.rs:1— `crates/openlogi-desktop/src/features/binding_editor.rs` and `crates/openlogi-desktop/src/features/mouse/view.rs` change together 59% of the time (19 of the 32 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 19 shared commits counted here, the most recent 3 are `10d25371` feat(gui): add custom actions to the mouse picker (#1452); `32ce1e8c` refactor(gui): clean up render paths and element ids (#926) (at that commit the file was still `crates/openlogi-desktop/src/features/mouse/picker.rs`); `279d7caf` feat(gui): make custom controls keyboard-operable (#916) (at that commit the file was still `crates/openlogi-desktop/src/features/mouse/picker.rs`) — run `git show` on any of them.
Change coupling: tests.rs ↔ keyboard.rs crates/openlogi-device/src/session/gesture/tests.rs:1— `crates/openlogi-device/src/session/gesture/tests.rs` and `crates/openlogi-device/src/session/keyboard.rs` change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `f4f1bb12` fix(device): omit raw-xy flags when diverting or restoring keyboard c…; `f412a1a2` refactor(device): share one pending-restore token between capture and…; `15d2656a` refactor(device): run gesture and keyboard capture through one sessio… — run `git show` on any of them.
Change coupling: dpi.rs ↔ smartshift.rs crates/openlogi-desktop/src/features/pointer/dpi.rs:1— `crates/openlogi-desktop/src/features/pointer/dpi.rs` and `crates/openlogi-desktop/src/features/pointer/smartshift.rs` change together 50% of the time (13 of the 26 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `263328b2` refactor(gui): fold the duplicate load accessors; `3fb347c3` refactor(gui): give device panels one relevance filter; `0832c069` refactor(gui): move device reads onto swr — run `git show` on any of them.
Change coupling: route.rs ↔ pairing.rs crates/openlogi-device/src/channel/route.rs:1— `crates/openlogi-device/src/channel/route.rs` and `crates/openlogi-device/src/pairing.rs` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `6a8a8f82` refactor(device): rename RECEIVER_REGISTER_WAIT to RECEIVER_REGISTER_…; `491ad2f9` fix(hid): every receiver register caller takes the node's register phase; `3878f033` refactor(hid): centralize device identities (#831) — run `git show` on any of them.
Change coupling: hook.rs ↔ bindings.rs crates/openlogi-agent-core/src/runtime/hook.rs:1— `crates/openlogi-agent-core/src/runtime/hook.rs` and `crates/openlogi-core/src/bindings.rs` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `39001463` feat(core,gui): allow middle click gesture mode (#1738); `dc883d0a` feat(agent): support dpi button gestures; `5d666b33` feat(agent): dispatch independent long-press actions (#961) — run `git show` on any of them.
Change coupling: orchestrator.rs ↔ button.rs crates/openlogi-agent-core/src/orchestrator.rs:1— `crates/openlogi-agent-core/src/orchestrator.rs` and `crates/openlogi-agent-core/src/runtime/button.rs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `04eb7d0e` fix(core,agent): chain swipes within one gesture-button hold (#1652); `1505c652` fix(agent): fall back to focus when the pointer target is unidentifie…; `9910ffc6` fix(macos): capture side-button gestures over HID++ (#722) — run `git show` on any of them.
Change coupling: action_ring.rs ↔ function_row.rs crates/openlogi-desktop/src/features/action_ring.rs:1— `crates/openlogi-desktop/src/features/action_ring.rs` and `crates/openlogi-desktop/src/features/keyboard/function_row.rs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `e36d29c7` feat(gui): add Power User actions to the Action Ring editor (#1445); `3fb347c3` refactor(gui): give device panels one relevance filter; `8d70a471` refactor(gui): let binding mutators report BindingsChanged themselves — run `git show` on any of them.
Change coupling: dpi.rs ↔ dpi.rs crates/openlogi-cli/src/cmd/diag/dpi.rs:1— `crates/openlogi-cli/src/cmd/diag/dpi.rs` and `crates/openlogi-desktop/src/features/pointer/dpi.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `a86f83f4` refactor(core): model dpi as domain type; `8d6f48b5` fix(hid): drive 0x2202 DPI and 0x8081 lighting, not just their predec… (at that commit the file was still `crates/openlogi-gui/src/components/dpi_panel.rs`); `33dbb711` fix: address code-review findings for device-reported DPI (at that commit the file was still `crates/openlogi-gui/src/components/dpi_panel.rs`) — run `git show` on any of them.
Duplicated block (6 lines × 2) crates/openlogi-desktop/src/app/home/views.rs:103— crates/openlogi-desktop/src/app/home/views.rs:103-108 | crates/openlogi-desktop/src/app/home/views.rs:138-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/openlogi-desktop/src/app/home/views.rs:240— crates/openlogi-desktop/src/app/home/views.rs:240-245 | crates/openlogi-desktop/src/app/home/views.rs:345-350 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/openlogi-desktop/src/features/keyboard/function_row.rs:591— crates/openlogi-desktop/src/features/keyboard/function_row.rs:591-596 | crates/openlogi-desktop/src/features/keyboard/function_row.rs:651-656 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/openlogi-desktop/src/features/lighting/visual.rs:34— crates/openlogi-desktop/src/features/lighting/visual.rs:34-39 | crates/openlogi-desktop/src/features/lighting/visual.rs:58-63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/openlogi-desktop/src/features/mouse/inspector.rs:178— crates/openlogi-desktop/src/features/mouse/inspector.rs:178-183 | crates/openlogi-desktop/src/features/mouse/inspector.rs:349-354 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) crates/openlogi-desktop/src/windows.rs:172— crates/openlogi-desktop/src/windows.rs:172-177 | crates/openlogi-desktop/src/windows/main_window.rs:62-68 — 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) xtask/src/commands/macos/bundle.rs:120— xtask/src/commands/macos/bundle.rs:120-125 | xtask/src/commands/macos/bundle/sparkle.rs:194-199 — 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/openlogi-desktop/src/features/mouse/view.rs:156— crates/openlogi-desktop/src/features/mouse/view.rs:156-161 | crates/openlogi-desktop/src/windows/settings.rs:197-202 — 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/openlogi-core/src/hid/smartshift.rs:104— crates/openlogi-core/src/hid/smartshift.rs:104-109 | crates/openlogi-core/src/hid/smartshift.rs:266-271 — 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.
openlogi_agent_core::watchers::foreground_app::spawn_native (cognitive 50) crates/openlogi-agent-core/src/watchers/foreground_app.rs:105— openlogi_agent_core::watchers::foreground_app::spawn_native has cognitive complexity 50 (threshold 15). Drivers by points: if/else 11 (36 pts), loops 3 (7 pts), match/switch 3 (7 pts) (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_agent_core::watchers::pairing::run_with (cognitive 34) crates/openlogi-agent-core/src/watchers/pairing.rs:125— openlogi_agent_core::watchers::pairing::run_with has cognitive complexity 34 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 4 (9 pts), loops 4 (8 pts) (nesting depth added 21). 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.
openlogi_agent_core::watchers::host_switch::manage (cognitive 32) crates/openlogi-agent-core/src/watchers/host_switch.rs:465— openlogi_agent_core::watchers::host_switch::manage has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_agent_core::runtime::hook::handle_button (cognitive 27) crates/openlogi-agent-core/src/runtime/hook.rs:240— openlogi_agent_core::runtime::hook::handle_button has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (26 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.
openlogi_agent_core::runtime::scroll::worker::run_worker (cognitive 23) crates/openlogi-agent-core/src/runtime/scroll/worker.rs:501— openlogi_agent_core::runtime::scroll::worker::run_worker has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 3 (8 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_agent_core::watchers::capture_manager::run (cognitive 23) crates/openlogi-agent-core/src/watchers/capture_manager.rs:94— openlogi_agent_core::watchers::capture_manager::run has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (13 pts), match/switch 4 (9 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_agent_core::orchestrator::devices::changed_follower_cookies (cognitive 17) crates/openlogi-agent-core/src/orchestrator/devices.rs:562— openlogi_agent_core::orchestrator::devices::changed_follower_cookies has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3, match/switch 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.
openlogi_agent_core::orchestrator::devices::plan_reapply (cognitive 17) crates/openlogi-agent-core/src/orchestrator/devices.rs:809— openlogi_agent_core::orchestrator::devices::plan_reapply has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (5 lines × 2) crates/openlogi-desktop/src/features/profiles.rs:145— crates/openlogi-desktop/src/features/profiles.rs:145-149 | crates/openlogi-desktop/src/features/profiles.rs:191-195 — 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/openlogi-device/src/write/dpi.rs:265— crates/openlogi-device/src/write/dpi.rs:265-269 | crates/openlogi-device/src/write/dpi.rs:345-349 — 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/openlogi-device/src/write/haptic.rs:93— crates/openlogi-device/src/write/haptic.rs:93-97 | crates/openlogi-device/src/write/lighting/rgb.rs:294-300 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/openlogi-device/src/write/hires_wheel.rs:196— crates/openlogi-device/src/write/hires_wheel.rs:196-200 | crates/openlogi-device/src/write/lighting/rgb.rs:284-288 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/openlogi-hook/src/macos/pointer.rs:29— crates/openlogi-hook/src/macos/pointer.rs:29-34 | crates/openlogi-inject/src/inject/macos/spaces.rs:663-667 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) crates/openlogi-inject/src/inject/macos.rs:303— crates/openlogi-inject/src/inject/macos.rs:303-309 | crates/openlogi-inject/src/inject/macos.rs:335-339 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/openlogi-desktop/src/app/home/views.rs:218— crates/openlogi-desktop/src/app/home/views.rs:218-222 | crates/openlogi-desktop/src/app/home/views.rs:256-260 — 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/openlogi-device/src/write/backlight.rs:258— crates/openlogi-device/src/write/backlight.rs:258-262 | crates/openlogi-device/src/write/backlight.rs:322-326 — 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.
Off the main sequence: openlogi-assets — openlogi-assets: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: openlogi-device-registry — openlogi-device-registry: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: openlogi-core — openlogi-core: abstractness 0.00, instability 0.07, distance 0.93 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
Off the main sequence: openlogi-fixture — openlogi-fixture: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: openlogi-camera — openlogi-camera: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: openlogi-ipc — openlogi-ipc: abstractness 0.10, instability 0.17, distance 0.74 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: openlogi-inject — openlogi-inject: abstractness 0.03, instability 0.25, distance 0.72 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
openlogi_device::pairing::drive (cyclomatic 24) crates/openlogi-device/src/pairing.rs:529— openlogi_device::pairing::drive 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.
openlogi_device::session::capture::monitor (cyclomatic 23) crates/openlogi-device/src/session/capture.rs:351— openlogi_device::session::capture::monitor 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.
openlogi_device::session::gesture::arm::arm_controls_into (cyclomatic 22) crates/openlogi-device/src/session/gesture/arm.rs:201— openlogi_device::session::gesture::arm::arm_controls_into 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.
openlogi_device::channel::route::open_route_channel (cyclomatic 18) crates/openlogi-device/src/channel/route.rs:44— openlogi_device::channel::route::open_route_channel has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
openlogi_device::pairing::open_receiver_with_inventory (cyclomatic 18) crates/openlogi-device/src/pairing.rs:321— openlogi_device::pairing::open_receiver_with_inventory has cyclomatic complexity 18 (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.
openlogi_device::inventory::cache::probe_or_reuse_registered (cyclomatic 16) crates/openlogi-device/src/inventory/cache.rs:197— openlogi_device::inventory::cache::probe_or_reuse_registered 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.
AppState::finish_light_command (cognitive 26) crates/openlogi-desktop/src/state/light.rs:310— AppState::finish_light_command has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (23 pts), loops 1 (3 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AppState::adopt_transient_records (cognitive 24) crates/openlogi-desktop/src/state/inventory.rs:317— AppState::adopt_transient_records has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppState::commit_light (cognitive 20) crates/openlogi-desktop/src/state/light.rs:534— AppState::commit_light has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AppState::adopt_changes_on_lights (cognitive 17) crates/openlogi-desktop/src/state/light.rs:421— AppState::adopt_changes_on_lights has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppState::refresh_inventories (cognitive 16) crates/openlogi-desktop/src/state/inventory.rs:62— AppState::refresh_inventories has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 4, boolean chains 3 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Duplicated block (11 lines × 2) crates/openlogi-agent/src/server.rs:1068— crates/openlogi-agent/src/bin/mock_agent.rs:268-278 | crates/openlogi-agent/src/server.rs:1068-1078 — 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 (11 lines × 2) crates/openlogi-agent/src/bin/mock_agent/profile.rs:28— crates/openlogi-agent/src/bin/mock_agent/profile.rs:28-38 | crates/openlogi-cli/src/cmd/fixture/record_profile.rs:433-443 — 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 (11 lines × 2) crates/openlogi-core/src/binding/key_combo.rs:49— crates/openlogi-core/src/binding/key_combo.rs:49-59 | crates/openlogi-inject/src/inject.rs:722-732 — 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 (11 lines × 2) crates/openlogi-overlay/src/backlight.rs:77— crates/openlogi-overlay/src/backlight.rs:77-87 | crates/openlogi-overlay/src/lock_key.rs:127-137 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) crates/openlogi-desktop/src/features/action_ring.rs:163— crates/openlogi-desktop/src/features/action_ring.rs:163-173 | crates/openlogi-desktop/src/features/action_ring.rs:186-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/openlogi-desktop/src/state/pointer_speed.rs:105— crates/openlogi-desktop/src/state/pointer_speed.rs:105-112 | crates/openlogi-desktop/src/state/report_rate.rs:73-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/openlogi-desktop/src/windows/add_device.rs:332— crates/openlogi-desktop/src/windows/add_device.rs:332-339 | crates/openlogi-desktop/src/windows/update_consent.rs:81-88 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) crates/openlogi-device/src/replay/barrier.rs:44— crates/openlogi-device/src/replay/barrier.rs:44-51 | crates/openlogi-device/src/replay/barrier.rs:72-79 — 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) crates/openlogi-desktop/src/features/mouse/view.rs:158— crates/openlogi-desktop/src/features/mouse/view.rs:158-165 | crates/openlogi-desktop/src/features/mouse/view.rs:169-178 — 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) crates/openlogi-fixture/src/protocol_identity.rs:431— crates/openlogi-fixture/src/protocol_identity.rs:431-438 | crates/openlogi-fixture/src/protocol_identity.rs:446-453 — 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.
openlogi_agent_core::watchers::host_switch::manage (cyclomatic 21) crates/openlogi-agent-core/src/watchers/host_switch.rs:465— openlogi_agent_core::watchers::host_switch::manage 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.
openlogi_agent_core::watchers::foreground_app::spawn_native (cyclomatic 19) crates/openlogi-agent-core/src/watchers/foreground_app.rs:105— openlogi_agent_core::watchers::foreground_app::spawn_native 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.
openlogi_agent_core::watchers::capture_manager::run (cyclomatic 17) crates/openlogi-agent-core/src/watchers/capture_manager.rs:94— openlogi_agent_core::watchers::capture_manager::run 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.
openlogi_agent_core::watchers::pairing::run_with (cyclomatic 17) crates/openlogi-agent-core/src/watchers/pairing.rs:125— openlogi_agent_core::watchers::pairing::run_with 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.
TooManyMethods: AppState crates/openlogi-desktop/src/state.rs:179— TooManyMethods — 285 methods, declared across 24 files: src/state.rs (29), state/settings.rs (29), state/bindings.rs (25), state/disable_keys.rs (20), +20 more file(s). The bar is 30 methods; this is 255 over it, 9.50× 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.
TooManyMethods: Config crates/openlogi-core/src/config.rs:125— TooManyMethods — 86 methods, declared across 8 files: config/per_device.rs (53), config/per_app.rs (8), src/config.rs (5), config/gestures.rs (5), +4 more file(s). The bar is 30 methods; this is 56 over it, 2.87× 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.
TooManyMethods: Orchestrator crates/openlogi-agent-core/src/orchestrator.rs:513— TooManyMethods — 71 methods, declared across 2 files: src/orchestrator.rs (62), orchestrator/lights.rs (9). The bar is 30 methods; this is 41 over it, 2.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.
TooManyMethods: DeviceReads crates/openlogi-desktop/src/services/device_reads.rs:66— TooManyMethods — 65 methods. The bar is 30 methods; this is 35 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DeviceReads crates/openlogi-desktop/src/services/device_reads.rs:66— ClassTooLong — 882 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 65 methods, 2 blocks, lines 66-1504. The bar is 400 significant lines; this is 482 over it, 2.21× 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: Orchestrator crates/openlogi-agent-core/src/orchestrator.rs:513— ClassTooLong — 840 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 71 methods, 2 blocks, lines 513-2035. The bar is 400 significant lines; this is 440 over it, 2.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.
ClassTooLong: CameraControlsPanel crates/openlogi-desktop/src/features/camera/controls.rs:69— ClassTooLong — 419 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 3 blocks, lines 69-778. The bar is 400 significant lines; this is 19 over it, 1.05× 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: MockAgent crates/openlogi-agent/src/bin/mock_agent.rs:909— ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 5 methods, 3 blocks, lines 909-1520. The bar is 400 significant lines; this is 12 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (7 lines × 2) crates/openlogi-desktop/src/features/profiles.rs:134— crates/openlogi-desktop/src/features/profiles.rs:134-140 | crates/openlogi-desktop/src/features/profiles.rs:179-185 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/openlogi-hook/src/windows/hook.rs:387— crates/openlogi-hook/src/windows/hook.rs:387-393 | crates/openlogi-hook/src/windows/hook.rs:528-534 — 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/openlogi-desktop/src/windows/settings/assets.rs:157— crates/openlogi-desktop/src/windows/settings/assets.rs:157-163 | crates/openlogi-desktop/src/windows/settings/language.rs:72-80 — 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) crates/openlogi-overlay/src/notice.rs:242— crates/openlogi-overlay/src/notice.rs:242-248 | crates/openlogi-overlay/src/session.rs:165-171 — 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.
openlogi_hook::linux::device_thread (cognitive 38) crates/openlogi-hook/src/linux.rs:506— openlogi_hook::linux::device_thread has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (31 pts), loops 2 (3 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_hook::linux::foreground::stop::poll_source_or_stop (cognitive 16) crates/openlogi-hook/src/linux/foreground/stop.rs:156— openlogi_hook::linux::foreground::stop::poll_source_or_stop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_hook::linux::pointer::context_on_connection (cognitive 16) crates/openlogi-hook/src/linux/pointer.rs:47— openlogi_hook::linux::pointer::context_on_connection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_overlay::main (cognitive 32) crates/openlogi-overlay/src/main.rs:51— openlogi_overlay::main has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 6 (9 pts), match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_overlay::ipc::send_commands_with (cognitive 28) crates/openlogi-overlay/src/ipc.rs:379— openlogi_overlay::ipc::send_commands_with has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 4 (8 pts), match/switch 2 (7 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_overlay::ipc::observe (cognitive 22) crates/openlogi-overlay/src/ipc.rs:281— openlogi_overlay::ipc::observe has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_camera::uvc_macos::scan_descriptors (cognitive 22) crates/openlogi-camera/src/uvc_macos.rs:646— openlogi_camera::uvc_macos::scan_descriptors has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5, match/switch 1 (3 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.
openlogi_camera::linux::max_format (cognitive 17) crates/openlogi-camera/src/linux.rs:275— openlogi_camera::linux::max_format has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_camera::capture_macos::open_session (cognitive 16) crates/openlogi-camera/src/capture_macos.rs:336— openlogi_camera::capture_macos::open_session has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openlogi_cli::cmd::diag::features::run (cognitive 21) crates/openlogi-cli/src/cmd/diag/features.rs:16— openlogi_cli::cmd::diag::features::run has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (11 pts), match/switch 3 (9 pts), if/else 1 (nesting depth added 13). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
openlogi_cli::cmd::list::run (cognitive 18) crates/openlogi-cli/src/cmd/list.rs:35— openlogi_cli::cmd::list::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.
openlogi_cli::cmd::assets::sync::run (cognitive 17) crates/openlogi-cli/src/cmd/assets/sync.rs:67— openlogi_cli::cmd::assets::sync::run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (4 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×3
Duplicated block (10 lines × 2) crates/openlogi-agent-core/src/runtime/button/worker.rs:145— crates/openlogi-agent-core/src/runtime/button/worker.rs:145-154 | crates/openlogi-agent-core/src/runtime/button/worker.rs:180-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/openlogi-hid/src/transport.rs:475— crates/openlogi-hid/src/transport.rs:475-484 | crates/openlogi-hid/src/transport.rs:496-505 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/openlogi-device/src/inventory/probe/bolt.rs:279— crates/openlogi-device/src/inventory/probe/bolt.rs:279-288 | crates/openlogi-device/src/inventory/probe/unifying.rs:338-347 — 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) crates/openlogi-desktop/src/features/mouse/view.rs:801— crates/openlogi-desktop/src/features/mouse/view.rs:801-809 | crates/openlogi-desktop/src/features/mouse/view/labels.rs:182-190 — 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 (9 lines × 2) crates/openlogi-agent-core/src/hardware.rs:712— crates/openlogi-agent-core/src/hardware.rs:712-720 | crates/openlogi-agent-core/src/hardware.rs:751-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.
Duplicated block (9 lines × 2) crates/openlogi-core/src/config/file.rs:476— crates/openlogi-core/src/config/file.rs:476-484 | crates/openlogi-core/src/config/file.rs:488-496 — 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.
openlogi_core::config::identity::fold (cyclomatic 47) crates/openlogi-core/src/config/identity.rs:247— openlogi_core::config::identity::fold has cyclomatic complexity 47 (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.
openlogi_core::binding::key_combo::parse_key (cyclomatic 33) crates/openlogi-core/src/binding/key_combo.rs:333— openlogi_core::binding::key_combo::parse_key has cyclomatic complexity 33 (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.
InventoryWorker::next_trigger (cognitive 34) crates/openlogi-agent-core/src/watchers/inventory.rs:612— InventoryWorker::next_trigger has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 5 (13 pts), boolean chains 2, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InventoryWorker::settle_trigger (cognitive 17) crates/openlogi-agent-core/src/watchers/inventory.rs:494— InventoryWorker::settle_trigger has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
openlogi_core::config::identity::fold (cognitive 31) crates/openlogi-core/src/config/identity.rs:247— openlogi_core::config::identity::fold has cognitive complexity 31 (threshold 15). Drivers by points: match/switch 15, if/else 10, boolean chains 5, loops 1. 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.
openlogi_core::config::identity::fold_maps (cognitive 28) crates/openlogi-core/src/config/identity.rs:382— openlogi_core::config::identity::fold_maps has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (24 pts), loops 4 (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.
openlogi_desktop::services::assets::glow::compute_glow_geometry (cognitive 26) crates/openlogi-desktop/src/services/assets/glow.rs:98— openlogi_desktop::services::assets::glow::compute_glow_geometry has cognitive complexity 26 (threshold 15). Drivers by points: loops 7 (12 pts), if/else 6 (11 pts), boolean chains 3 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
openlogi_desktop::features::camera::controls::rows::control_row (cognitive 22) crates/openlogi-desktop/src/features/camera/controls/rows.rs:85— openlogi_desktop::features::camera::controls::rows::control_row has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 4 (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.
CameraControlsPanel::apply_profile (cognitive 25) crates/openlogi-desktop/src/features/camera/controls.rs:595— CameraControlsPanel::apply_profile has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 4 (8 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CameraControlsPanel::ensure_built (cognitive 16) crates/openlogi-desktop/src/features/camera/controls.rs:195— CameraControlsPanel::ensure_built has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), loops 4, match/switch 3 (4 pts), boolean chains 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.
Config::migrate_owner_locked_gestures (cognitive 24) crates/openlogi-core/src/config/migrate.rs:77— Config::migrate_owner_locked_gestures has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (15 pts), match/switch 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Config::migrate_thumbwheel_native_direction (cognitive 18) crates/openlogi-core/src/config/migrate.rs:224— Config::migrate_thumbwheel_native_direction has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 3, loops 2 (3 pts), match/switch 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.
KeyboardManagerState::reconcile (cognitive 22) crates/openlogi-agent-core/src/watchers/keyboard.rs:255— KeyboardManagerState::reconcile has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 2, match/switch 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.
KeyboardManagerState::handle_session_event (cognitive 17) crates/openlogi-agent-core/src/watchers/keyboard.rs:339— KeyboardManagerState::handle_session_event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Enumerator::enumerate_reporting_completeness (cognitive 22) crates/openlogi-device/src/inventory.rs:606— Enumerator::enumerate_reporting_completeness has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 4, loops 3 (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.
Enumerator::prepare_nodes (cognitive 16) crates/openlogi-device/src/inventory.rs:438— Enumerator::prepare_nodes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GestureManagerState::reconcile (cognitive 18) crates/openlogi-agent-core/src/watchers/gesture.rs:399— GestureManagerState::reconcile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 2, match/switch 1 (2 pts) (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.
GestureManagerState::handle_session_event (cognitive 16) crates/openlogi-agent-core/src/watchers/gesture.rs:484— GestureManagerState::handle_session_event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, match/switch 1 (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.
Rename::lock (cognitive 18) xtask/src/commands/release/stamp_version.rs:403— Rename::lock has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Rename::member (cognitive 17) xtask/src/commands/release/stamp_version.rs:335— Rename::member has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
xtask::commands::macos::dev_bundle::processes::reap_leftovers (cognitive 17) xtask/src/commands/macos/dev_bundle/processes.rs:35— xtask::commands::macos::dev_bundle::processes::reap_leftovers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
xtask::commands::lint::allow_sites::outer_attributes (cognitive 16) xtask/src/commands/lint/allow_sites.rs:147— xtask::commands::lint::allow_sites::outer_attributes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×2
Duplicated block (14 lines × 2) crates/openlogi-desktop/src/state/light.rs:583— crates/openlogi-desktop/src/state/light.rs:583-596 | crates/openlogi-desktop/src/state/light.rs:660-673 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/openlogi-desktop/src/features/profiles.rs:158— crates/openlogi-desktop/src/features/profiles.rs:158-171 | crates/openlogi-desktop/src/features/profiles.rs:204-217 — 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 × 3) crates/openlogi-desktop/src/services/device_reads.rs:593— crates/openlogi-desktop/src/services/device_reads.rs:593-597 | crates/openlogi-desktop/src/services/device_reads.rs:704-708 | crates/openlogi-desktop/src/services/device_reads.rs:812-816 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) crates/openlogi-device/src/write/diagnostics.rs:68— crates/openlogi-device/src/write/diagnostics.rs:68-72 | crates/openlogi-device/src/write/smartshift.rs:404-408 | crates/openlogi-device/src/write/smartshift.rs:427-431 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
EventFeatureIndices::recognizes (cyclomatic 29) crates/openlogi-device/src/inventory/events.rs:400— EventFeatureIndices::recognizes has cyclomatic complexity 29 (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.
InventoryWorker::next_trigger (cyclomatic 20) crates/openlogi-agent-core/src/watchers/inventory.rs:612— InventoryWorker::next_trigger 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.
CaptureAccum::on_event (cyclomatic 20) crates/openlogi-device/src/session/gesture/accum.rs:112— CaptureAccum::on_event 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.
ActionExecutor::dispatch_to (cyclomatic 19) crates/openlogi-agent-core/src/runtime.rs:144— ActionExecutor::dispatch_to 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.
SwipeAccumulator::accumulate (cyclomatic 19) crates/openlogi-core/src/binding/swipe.rs:147— SwipeAccumulator::accumulate 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.
RingHapticPlayer::spawn (cyclomatic 18) crates/openlogi-agent/src/server.rs:893— RingHapticPlayer::spawn has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InputDispatcher::dispatch (cyclomatic 18) crates/openlogi-agent-core/src/watchers/gesture/dispatch.rs:149— InputDispatcher::dispatch has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppView::repaints_for (cyclomatic 18) crates/openlogi-desktop/src/app.rs:330— AppView::repaints_for has cyclomatic complexity 18 (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.
KeyboardManagerState::reconcile (cyclomatic 17) crates/openlogi-agent-core/src/watchers/keyboard.rs:255— KeyboardManagerState::reconcile 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.
ReceiverSlots::validate (cyclomatic 17) crates/openlogi-device/src/replay/slots.rs:48— ReceiverSlots::validate has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
openlogi_overlay::main (cyclomatic 17) crates/openlogi-overlay/src/main.rs:51— openlogi_overlay::main 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.
DetailTab::tabs_for (cyclomatic 16) crates/openlogi-desktop/src/app.rs:105— DetailTab::tabs_for has cyclomatic complexity 16 (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.
AppState::adopt_transient_records (cyclomatic 16) crates/openlogi-desktop/src/state/inventory.rs:317— AppState::adopt_transient_records 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.
openlogi_desktop::services::assets::glow::compute_glow_geometry (cyclomatic 16) crates/openlogi-desktop/src/services/assets/glow.rs:98— openlogi_desktop::services::assets::glow::compute_glow_geometry has cyclomatic complexity 16 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Accumulator::run (cyclomatic 16) crates/openlogi-hid/src/recording/accumulator.rs:64— Accumulator::run 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.
CaptureAccum::on_event (cognitive 34) crates/openlogi-device/src/session/gesture/accum.rs:112— CaptureAccum::on_event has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 6, loops 3 (6 pts), match/switch 3 (6 pts) (nesting depth added 15). 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.
RingHapticPlayer::spawn (cognitive 32) crates/openlogi-agent/src/server.rs:893— RingHapticPlayer::spawn has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (20 pts), match/switch 3 (6 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwipeAccumulator::accumulate (cognitive 30) crates/openlogi-core/src/binding/swipe.rs:147— SwipeAccumulator::accumulate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 4, match/switch 1 (nesting depth added 13). 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.
EventFeatureIndices::recognizes (cognitive 28) crates/openlogi-device/src/inventory/events.rs:400— EventFeatureIndices::recognizes has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 14, if/else 14. 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.
LightWatch::next (cognitive 28) crates/openlogi-device/src/write/litra/link.rs:238— LightWatch::next has cognitive complexity 28 (threshold 15). Drivers by points: match/switch 4 (14 pts), if/else 5 (10 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 16). 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.
ActionExecutor::dispatch_to (cognitive 27) crates/openlogi-agent-core/src/runtime.rs:144— ActionExecutor::dispatch_to has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (23 pts), match/switch 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InputDispatcher::dispatch (cognitive 24) crates/openlogi-agent-core/src/watchers/gesture/dispatch.rs:149— InputDispatcher::dispatch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 2, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HostSwitchManagerState::reconcile_recoveries (cognitive 21) crates/openlogi-agent-core/src/watchers/host_switch.rs:283— HostSwitchManagerState::reconcile_recoveries has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, loops 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Accumulator::run (cognitive 21) crates/openlogi-hid/src/recording/accumulator.rs:64— Accumulator::run has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppView::render_content (cognitive 20) crates/openlogi-desktop/src/app.rs:565— AppView::render_content has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ReceiverSlots::validate (cognitive 18) crates/openlogi-device/src/replay/slots.rs:48— ReceiverSlots::validate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 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.
WlrForeignToplevelSource::observe (cognitive 18) crates/openlogi-hook/src/linux/foreground/wlr_foreign_toplevel.rs:494— WlrForeignToplevelSource::observe has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Counts::from_cargo_json (cognitive 18) xtask/src/commands/lint/sweep.rs:196— Counts::from_cargo_json has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Booted::gate (cognitive 16) crates/openlogi-agent/src/lifecycle.rs:143— Booted::gate has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (8 pts), if/else 4 (7 pts), loops 1 (nesting depth added 8). 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.
Orchestrator::refresh_inventory_inner (cognitive 16) crates/openlogi-agent-core/src/orchestrator.rs:1111— Orchestrator::refresh_inventory_inner has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 5, boolean chains 4 (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.
LifecycleWatchdog::evaluate (cognitive 16) crates/openlogi-hook/src/macos/watchdog.rs:266— LifecycleWatchdog::evaluate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, boolean chains 2, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TooManyFunctions: openlogi_hid::host crates/openlogi-hid/src/host.rs:40— TooManyFunctions — 38 free functions. The bar is 30 free functions; this is 8 over it, 1.27× 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.
MethodTooLong: AppView.render_content crates/openlogi-desktop/src/app.rs:565— MethodTooLong — render_content runs 115 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 15 over it, 1.15× 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: openlogi_overlay::main crates/openlogi-overlay/src/main.rs:51— FunctionTooLong — openlogi_overlay::main runs 112 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 12 over it, 1.12× 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.
Near-duplicate member pair (26 shared lines) crates/openlogi-desktop/src/features/profiles.rs:133— crates/openlogi-desktop/src/features/profiles.rs:133-171 | crates/openlogi-desktop/src/features/profiles.rs:178-217 — These two members are variants of one another: 26 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) crates/openlogi-desktop/src/services/device_reads.rs:176— crates/openlogi-desktop/src/services/device_reads.rs:176-221 | crates/openlogi-desktop/src/services/device_reads.rs:339-387 | crates/openlogi-desktop/src/services/device_reads.rs:424-479 | crates/openlogi-desktop/src/services/device_reads.rs:558-613 | crates/openlogi-desktop/src/services/device_reads.rs:669-724 | crates/openlogi-desktop/src/services/device_reads.rs:780-832 | crates/openlogi-desktop/src/services/device_reads.rs:953-1008 — These 7 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 7 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 7 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/openlogi-agent-core/src/action_ring.rs:209— crates/openlogi-agent-core/src/action_ring.rs:209-217 | crates/openlogi-agent-core/src/backlight_overlay.rs:68-75 | crates/openlogi-agent-core/src/lock_keys.rs:82-89 | crates/openlogi-agent-core/src/observable.rs:128-137 — 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.
Duplicated block (11–16 lines × 2) crates/openlogi-agent-core/src/orchestrator/devices.rs:209— crates/openlogi-agent-core/src/orchestrator/devices.rs:209-224 | crates/openlogi-agent-core/src/orchestrator/devices.rs:245-255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14–15 lines × 2) crates/openlogi-device/src/channel/route.rs:71— crates/openlogi-device/src/channel/route.rs:71-84 | crates/openlogi-device/src/channel/route.rs:87-101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–14 lines × 2) crates/openlogi-desktop/src/features/keyboard/function_row.rs:706— crates/openlogi-desktop/src/features/keyboard/function_row.rs:706-716 | crates/openlogi-desktop/src/features/mouse/leader_lines.rs:118-131 — 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 (13 lines × 3) crates/openlogi-device/src/inventory/standalone.rs:35— crates/openlogi-device/src/inventory/standalone.rs:35-47 | crates/openlogi-device/src/inventory/standalone.rs:62-74 | crates/openlogi-device/src/inventory/standalone.rs:89-101 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10–12 lines × 2) crates/openlogi-desktop/src/state/devices.rs:240— crates/openlogi-desktop/src/state/devices.rs:240-251 | crates/openlogi-desktop/src/state/devices.rs:484-493 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 2) crates/openlogi-inject/src/inject/macos.rs:125— crates/openlogi-inject/src/inject/macos.rs:125-136 | crates/openlogi-inject/src/inject/windows.rs:100-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10–11 lines × 7) crates/openlogi-desktop/src/services/device_reads.rs:181— crates/openlogi-desktop/src/services/device_reads.rs:181-190 | crates/openlogi-desktop/src/services/device_reads.rs:348-357 | crates/openlogi-desktop/src/services/device_reads.rs:433-443 | crates/openlogi-desktop/src/services/device_reads.rs:567-577 | crates/openlogi-desktop/src/services/device_reads.rs:678-688 | crates/openlogi-desktop/src/services/device_reads.rs:789-798 | crates/openlogi-desktop/src/services/device_reads.rs:962-972 — all 7 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 (10–11 lines × 2) crates/openlogi-desktop/src/features/mouse/inspector.rs:350— crates/openlogi-desktop/src/features/mouse/inspector.rs:350-359 | crates/openlogi-desktop/src/features/mouse/inspector.rs:411-421 — 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 (3–5 lines × 4) crates/openlogi-agent-core/src/action_ring.rs:212— crates/openlogi-agent-core/src/action_ring.rs:212-217 | crates/openlogi-agent-core/src/backlight_overlay.rs:71-75 | crates/openlogi-agent-core/src/lock_keys.rs:85-89 | crates/openlogi-agent-core/src/observable.rs:130-132 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (9 lines × 8) crates/openlogi-desktop/src/services/device_reads.rs:533— crates/openlogi-desktop/src/services/device_reads.rs:533-541 | crates/openlogi-desktop/src/services/device_reads.rs:643-651 | crates/openlogi-desktop/src/services/device_reads.rs:754-762 | crates/openlogi-desktop/src/services/device_reads.rs:927-935 | crates/openlogi-desktop/src/services/device_reads.rs:1113-1121 | crates/openlogi-desktop/src/services/device_reads.rs:1185-1193 | crates/openlogi-desktop/src/services/device_reads.rs:1226-1234 | crates/openlogi-desktop/src/services/disable_keys_reads.rs:127-135 — there are 8 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 8 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 5) crates/openlogi-desktop/src/state/backlight.rs:98— crates/openlogi-desktop/src/state/backlight.rs:98-103 | crates/openlogi-desktop/src/state/easy_switch.rs:54-59 | crates/openlogi-desktop/src/state/force_sensing.rs:36-41 | crates/openlogi-desktop/src/state/pointer_speed.rs:40-45 | crates/openlogi-desktop/src/state/report_rate.rs:38-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
Duplicated block (7 lines × 11) crates/openlogi-device/src/write/backlight.rs:241— crates/openlogi-device/src/write/backlight.rs:241-247 | crates/openlogi-device/src/write/diagnostics.rs:328-334 | crates/openlogi-device/src/write/disable_keys.rs:128-134 | crates/openlogi-device/src/write/dpi.rs:212-218 | crates/openlogi-device/src/write/dpi.rs:253-259 | crates/openlogi-device/src/write/easy_switch.rs:211-217 | crates/openlogi-device/src/write/fn_lock.rs:232-238 | crates/openlogi-device/src/write/hires_wheel.rs:27-33 | crates/openlogi-device/src/write/report_rate.rs:229-235 | crates/openlogi-device/src/write/smartshift.rs:374-380 | crates/openlogi-device/src/write/smartshift.rs:449-455 — there are 11 copies across 9 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 11 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 5) crates/openlogi-device/src/write/backlight.rs:301— crates/openlogi-device/src/write/backlight.rs:301-307 | crates/openlogi-device/src/write/dpi.rs:311-317 | crates/openlogi-device/src/write/fn_lock.rs:266-272 | crates/openlogi-device/src/write/report_rate.rs:260-266 | crates/openlogi-device/src/write/smartshift.rs:522-528 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
Duplicated block (6 lines × 3) crates/openlogi-device/src/write/easy_switch.rs:200— crates/openlogi-device/src/write/easy_switch.rs:200-205 | crates/openlogi-device/src/write/force_sensing.rs:127-132 | crates/openlogi-device/src/write/pointer_scaling.rs:136-141 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (16 lines × 2) crates/openlogi-desktop/src/state/bindings.rs:483— crates/openlogi-desktop/src/state/bindings.rs:483-500 | crates/openlogi-desktop/src/state/bindings.rs:531-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) crates/openlogi-desktop/src/features/mouse/inspector.rs:243— crates/openlogi-desktop/src/features/mouse/inspector.rs:243-257 | crates/openlogi-desktop/src/features/mouse/inspector.rs:448-462 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) crates/openlogi-desktop/src/features/mouse/inspector.rs:880— crates/openlogi-desktop/src/features/mouse/inspector.rs:880-892 | crates/openlogi-desktop/src/features/mouse/inspector.rs:939-951 — 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 (20 lines × 2) crates/openlogi-fixture/src/verify.rs:372— crates/openlogi-fixture/src/verify.rs:372-391 | crates/openlogi-fixture/src/verify.rs:411-430 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: MockAgent (LCOM4 4) crates/openlogi-agent/src/bin/mock_agent.rs:909— MockAgent's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Interpolated log message defeats structured logging crates/openlogi-overlay/src/ipc.rs:213— `info!` at line 213 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-overlay/src/ipc.rs:316— `debug!` at line 316 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-overlay/src/platform/windows/native.rs:241— `debug!` at line 241 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:495— `warn!` at line 495 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:574— `warn!` at line 574 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:858— `warn!` at line 858 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:864— `warn!` at line 864 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:887— `warn!` at line 887 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:964— `warn!` at line 964 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1002— `warn!` at line 1002 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1036— `warn!` at line 1036 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1041— `warn!` at line 1041 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1046— `warn!` at line 1046 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1058— `warn!` at line 1058 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1079— `warn!` at line 1079 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1118— `debug!` at line 1118 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1129— `debug!` at line 1129 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-inject/src/inject/linux.rs:1135— `warn!` at line 1135 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-hook/src/linux.rs:133— `error!` at line 133 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-hook/src/linux.rs:163— `debug!` at line 163 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-hook/src/linux.rs:185— `debug!` at line 185 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-hook/src/linux.rs:301— `error!` at line 301 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-hook/src/linux.rs:518— `warn!` at line 518 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-hook/src/linux.rs:538— `debug!` at line 538 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/openlogi-hook/src/linux.rs:551— `error!` at line 551 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Duplicated predicate crates/openlogi-cli/src/cmd/api.rs:455— `args.mode.is_some() || args.auto_disengage.is_some()` appears character-identically in 2 files — crates/openlogi-cli/src/cmd/api.rs, crates/openlogi-cli/src/cmd/api/persistence.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/openlogi-inject/src/inject.rs:190— `combo.has_command() || combo.has_control()` appears character-identically in 2 files — crates/openlogi-inject/src/inject.rs, crates/openlogi-inject/src/inject/linux.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/openlogi-inject/src/inject.rs:186— `combo.has_command() || combo.has_super()` appears character-identically in 3 files — crates/openlogi-inject/src/inject.rs, crates/openlogi-inject/src/inject/macos.rs, crates/openlogi-inject/src/inject/macos/menu_shortcut.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/openlogi-device-registry/src/headset.rs:72— `device.vendor_id == vendor_id && device.product_id == product_id && device.usage_page == usage_page && device.usage_id == usage_id` appears character-identically in 2 files — crates/openlogi-device-registry/src/headset.rs, crates/openlogi-device-registry/src/litra.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/openlogi-hidpp/src/feature/hires_wheel.rs:84— `header.device_index != device_index || header.feature_index != feature_index || header.software_id.to_lo() != 0` appears character-identically in 2 files — crates/openlogi-hidpp/src/feature/hires_wheel.rs, crates/openlogi-hidpp/src/feature/reprog_controls/event.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/openlogi-device/src/write/force_sensing/tests.rs:62— `self.fails_read_back && !self.writes.is_empty()` appears character-identically in 3 files — crates/openlogi-device/src/write/force_sensing/tests.rs, crates/openlogi-device/src/write/pointer_scaling/tests.rs, crates/openlogi-device/src/write/report_rate/tests.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/openlogi-device/src/session/host_switch.rs:1164— `slot.status == HostSlotStatus::Empty && slot.name_len == 0` appears character-identically in 2 files — crates/openlogi-device/src/session/host_switch.rs, crates/openlogi-device/src/session/host_switch/hosts.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 crates/openlogi-agent/src/overlay.rs:187— `overlay_images` 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 crates/openlogi-camera/src/linux.rs:46— `nodes` 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 xtask/src/commands/macos/dev_bundle/signing.rs:124— `development_identities` turns every `Err` into `Ok(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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 194 significant file(s) lose their only recent owner: crates/openlogi-desktop/src/services/device_reads.rs, crates/openlogi-desktop/src/services/ipc.rs, crates/openlogi-device/src/write/haptic.rs, crates/openlogi-fixture/src/schema.rs, crates/openlogi-desktop/src/runtime.rs, crates/openlogi-desktop/src/features/camera/controls.rs, crates/openlogi-desktop/src/state/light.rs, crates/openlogi-ipc/src/client.rs (+186 more). Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (195 single-owned of 611 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 611 of the 723 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: crates/openlogi-cli/src/cmd/diag/wheel.rs.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 4 of 20 project(s) overshoot their size bounds, lowering Project Cohesion to 6.0/10. The most over is `crates/openlogi-desktop` (49481 LoC, 185 module-visible types across 25 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
M2 · Architecture documentation· ADRs not easily discoverable · ×1
ADRs not easily discoverable — 1 ADR-shaped document(s) detected by content — `docs/DECISIONS.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
Logging is not universal — Only 14/16 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/openlogi`, `xtask`.
Outdated: anyhow — `anyhow` is locked at 1.0.103 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in xtask/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: async-trait — `async-trait` is locked at 0.1.89 but 0.1.92 is the current stable release on crates.io, and it already satisfies the `"0.1.88"` requirement declared in crates/openlogi-hidpp/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p async-trait` and commit the updated REDACTED.
Outdated: atomic-write-file — `atomic-write-file` is locked at 0.3.0 but 0.3.1 is the current stable release on crates.io, and it already satisfies the `"0.3.0"` requirement declared in crates/openlogi-assets/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p atomic-write-file` and commit the updated REDACTED.
Outdated: bitflags — `bitflags` is locked at 2.13.1 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in crates/openlogi-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` 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"` requirement declared in xtask/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: comfy-table — `comfy-table` is locked at 8.0.0 but 8.0.1 is the current stable release on crates.io, and it already satisfies the `"8.0.0"` requirement declared in xtask/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p comfy-table` and commit the updated REDACTED.
Outdated: core-foundation — `core-foundation` is locked at 0.10.0 but 0.10.1 is the current stable release on crates.io, and it already satisfies the `"0.10"` requirement declared in crates/openlogi-hook/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p core-foundation` and commit the updated REDACTED.
Outdated: disclaim — `disclaim` is locked at 0.1.0 but 0.1.1 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in crates/openlogi-desktop/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p disclaim` and commit the updated REDACTED.
Outdated: embed-resource — `embed-resource` is locked at 3.0.9 but 3.0.12 is the current stable release on crates.io, and it already satisfies the `"3.0.9"` requirement declared in crates/openlogi-agent/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p embed-resource` and commit the updated REDACTED.
Outdated: fs-err — `fs-err` is locked at 3.3.0 but 3.3.2 is the current stable release on crates.io, and it already satisfies the `"3.3.0"` requirement declared in xtask/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p fs-err` and commit the updated REDACTED.
Outdated: futures — `futures` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/openlogi-agent/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures` and commit the updated REDACTED.
Outdated: interprocess — `interprocess` is locked at 2.4.2 but 2.4.7 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in crates/openlogi-agent/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p interprocess` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.186 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in crates/openlogi-agent/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` 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/openlogi-agent/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p objc2` and commit the updated REDACTED.
Outdated: plist — `plist` is locked at 1.10.0 but 1.10.3 is the current stable release on crates.io, and it already satisfies the `"1.10.0"` requirement declared in xtask/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p plist` and commit the updated REDACTED.
Outdated: rust-i18n — `rust-i18n` is locked at 4.2.1 but 4.2.4 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/openlogi-agent/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rust-i18n` 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"` requirement declared in xtask/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"` requirement declared in xtask/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: thiserror — `thiserror` is locked at 2.0.18 but 2.0.21 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in crates/openlogi-assets/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p thiserror` and commit the updated REDACTED.
Outdated: time — `time` is locked at 0.3.47 but 0.3.55 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in xtask/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p time` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.53.3 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/openlogi-agent-core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: ureq — `ureq` is locked at 3.3.0 but 3.5.0 is the current stable release on crates.io, and it already satisfies the `"3"` requirement declared in crates/openlogi-assets/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ureq` and commit the updated REDACTED.
Outdated: wayland-client — `wayland-client` is locked at 0.31.14 but 0.31.15 is the current stable release on crates.io, and it already satisfies the `"0.31"` requirement declared in crates/openlogi-hook/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wayland-client` and commit the updated REDACTED.
Outdated: which — `which` is locked at 8.0.4 but 8.0.6 is the current stable release on crates.io, and it already satisfies the `"8.0.4"` requirement declared in xtask/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p which` and commit the updated REDACTED.
Outdated: zune-core — `zune-core` is locked at 0.5.1 but 0.5.3 is the current stable release on crates.io, and it already satisfies the `"0.5"` requirement declared in crates/openlogi-camera/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zune-core` 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.
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 01a17ac2-dc87-7da8-9fe7-9e351f4c85a2 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 106 · Warnings: 281 · Recommendations: 57 · Info: 25 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 27-10-2026 @ 00:29 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.