Public report of alex-oleshkevich/glimpse, published 17 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 17 November 2026, 12:00 UTC · Survey ID cd_c7d1798e0b2b4648ac8e2fc4d2742dbb
alex-oleshkevich/glimpse
Measured 17 November 2026, 11:57 UTC, at code version 2d56053
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureRanButNoData).
CAI scoreAt risk
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: 201,071 lines of product code in 29 projects, tests not counted · Estimated rebuild effort: about 2.3 person-years · Weakest lens: Code Health, 67.6
Findings by how serious they are
77 critical824 serious108 minor
9 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 11:57 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
73of 73 dimensions measured by tools.
973of 1009 findings point to an exact file and line, so you can open each one in the code. The other 36 concern the repository as a whole, such as missing documentation.
73dimensions across 8 lenses, read from 201,071 lines of product code in 29 projects.
alex-oleshkevich/glimpse is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 72.8 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step is making the work cancellable, worth about 2.8 points. Automating dependency updates comes next, worth about 2.5 points.
Fifty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One known security hole in a package the code depends on can be used by attackers, and one pipeline step installs packages that can change without warning. Pinning each tool to an exact version, updating the vulnerable packages and pinning what the pipeline installs would close these risks. Saving the change and the message together would take care of the place where data is saved and a message sent separately.
The product code is 201,071 lines, about €340,000 to rebuild.
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 84%Tests 16%
Rebuild cost: about €340,000 · Estimate
Cost to rebuild
€110,000 to €560,000, for 1,856 to 5,888 hours of work, about 2.3 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 73. 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: 201,071 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
Keep-a-Changelog) recording what shipped in each release.
Raises the score by about 1.9 points · Medium effort · Release Hygiene
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
Thread a context.Context through functions that make requests, so the work stops when its caller gives up. Of all the actions in this report, it raises the score most for the work it takes: about 2.8 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.9 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 6% on every change. The history of the code shows how much it changes: about 756,759 lines over the last 90 days, which is about 3,069,078 lines a year. At that pace, the extra work comes to an estimated 209.5 to 1257.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
591 modules, with 1196 dependencies between them. 15 loops run through 49 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 551 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.
glimpse_agents.app uses glimpse_compositors.model, so a change to glimpse_compositors.model can break glimpse_agents.app, while a change to glimpse_agents.app can't break glimpse_compositors.model.
Position
Below the diagonal: glimpse_agents.app uses a module listed above it, which is the healthy direction.
glimpse_config.schema uses glimpse_config.schema.applets, so a change to glimpse_config.schema.applets can break glimpse_config.schema, while a change to glimpse_config.schema can't break glimpse_config.schema.applets.
Position
Below the diagonal: glimpse_config.schema uses a module listed above it, which is the healthy direction.
glimpse_dbus.clients.weather uses glimpse_dbus.provider, so a change to glimpse_dbus.provider can break glimpse_dbus.clients.weather, while a change to glimpse_dbus.clients.weather can't break glimpse_dbus.provider.
Position
Below the diagonal: glimpse_dbus.clients.weather uses a module listed above it, which is the healthy direction.
17→36 glimpse_panel.applet.popover uses glimpse_panel.appletpart of a loop✕
Connections
1 pair of types, where a type in glimpse_panel.applet.popover uses a type in glimpse_panel.applet.
glimpse_panel.applet.popover uses glimpse_panel.applet, so a change to glimpse_panel.applet can break glimpse_panel.applet.popover, while a change to glimpse_panel.applet.popover can't break glimpse_panel.applet.
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.
glimpse_services.context uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.context, while a change to glimpse_services.context can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.context uses a module listed above it, which is the healthy direction.
glimpse_services.services.bluetooth.failure uses glimpse_compositors.contract, so a change to glimpse_compositors.contract can break glimpse_services.services.bluetooth.failure, while a change to glimpse_services.services.bluetooth.failure can't break glimpse_compositors.contract.
Position
Below the diagonal: glimpse_services.services.bluetooth.failure uses a module listed above it, which is the healthy direction.
glimpse_shot.gui.canvas uses glimpse_compositors.model, so a change to glimpse_compositors.model can break glimpse_shot.gui.canvas, while a change to glimpse_shot.gui.canvas can't break glimpse_compositors.model.
Position
Below the diagonal: glimpse_shot.gui.canvas uses a module listed above it, which is the healthy direction.
glimpse_shot.gui.canvas uses glimpse_shot.doc.document, so a change to glimpse_shot.doc.document can break glimpse_shot.gui.canvas, while a change to glimpse_shot.gui.canvas can't break glimpse_shot.doc.document.
Position
Below the diagonal: glimpse_shot.gui.canvas uses a module listed above it, which is the healthy direction.
glimpse_services.services.brightness uses glimpse_compositors.contract, so a change to glimpse_compositors.contract can break glimpse_services.services.brightness, while a change to glimpse_services.services.brightness can't break glimpse_compositors.contract.
Position
Below the diagonal: glimpse_services.services.brightness uses a module listed above it, which is the healthy direction.
glimpse_services.services.brightness uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.brightness, while a change to glimpse_services.services.brightness can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.brightness uses a module listed above it, which is the healthy direction.
glimpse_services.services.brightness uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.brightness, while a change to glimpse_services.services.brightness can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.brightness uses a module listed above it, which is the healthy direction.
21→24 glimpse_services.services.brightness uses glimpse_services.subscriptionpart of a loop✕
Connections
1 pair of types, where a type in glimpse_services.services.brightness uses a type in glimpse_services.subscription.
glimpse_services.services.brightness uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.brightness, while a change to glimpse_services.services.brightness can't break glimpse_services.subscription.
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.
21→25 glimpse_services.services.brightness uses glimpse_services.services.bluetoothpart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.brightness uses a type in glimpse_services.services.bluetooth.
glimpse_services.services.brightness uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.brightness, while a change to glimpse_services.services.brightness can't break glimpse_services.services.bluetooth.
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.
21→26 glimpse_services.services.brightness uses glimpse_services.services.batterypart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.brightness uses a type in glimpse_services.services.battery.
glimpse_services.services.brightness uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.brightness, while a change to glimpse_services.services.brightness can't break glimpse_services.services.battery.
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.
21→28 glimpse_services.services.brightness uses glimpse_services.services.audio.pulsepart of a loop✕
Connections
1 pair of types, where a type in glimpse_services.services.brightness uses a type in glimpse_services.services.audio.pulse.
glimpse_services.services.brightness uses glimpse_services.services.audio.pulse, so a change to glimpse_services.services.audio.pulse can break glimpse_services.services.brightness, while a change to glimpse_services.services.brightness can't break glimpse_services.services.audio.pulse.
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.
21→34 glimpse_services.services.brightness uses glimpse_services.servicepart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.brightness uses a type in glimpse_services.service.
glimpse_services.services.brightness uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.brightness, while a change to glimpse_services.services.brightness can't break glimpse_services.service.
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.
glimpse_shot.gui.overlay uses glimpse_compositors.contract, so a change to glimpse_compositors.contract can break glimpse_shot.gui.overlay, while a change to glimpse_shot.gui.overlay can't break glimpse_compositors.contract.
Position
Below the diagonal: glimpse_shot.gui.overlay uses a module listed above it, which is the healthy direction.
glimpse_shot.gui.overlay uses glimpse_shot.doc.document, so a change to glimpse_shot.doc.document can break glimpse_shot.gui.overlay, while a change to glimpse_shot.gui.overlay can't break glimpse_shot.doc.document.
Position
Below the diagonal: glimpse_shot.gui.overlay uses a module listed above it, which is the healthy direction.
glimpse_shot.gui.overlay uses glimpse_shot.ports, so a change to glimpse_shot.ports can break glimpse_shot.gui.overlay, while a change to glimpse_shot.gui.overlay can't break glimpse_shot.ports.
Position
Below the diagonal: glimpse_shot.gui.overlay uses a module listed above it, which is the healthy direction.
glimpse_shot.gui.overlay uses glimpse_shot.gui.canvas, so a change to glimpse_shot.gui.canvas can break glimpse_shot.gui.overlay, while a change to glimpse_shot.gui.overlay can't break glimpse_shot.gui.canvas.
Position
Below the diagonal: glimpse_shot.gui.overlay uses a module listed above it, which is the healthy direction.
glimpse_services.services.exec uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.exec, while a change to glimpse_services.services.exec can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.exec uses a module listed above it, which is the healthy direction.
glimpse_services.services.exec uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.exec, while a change to glimpse_services.services.exec can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.exec uses a module listed above it, which is the healthy direction.
glimpse_services.services.exec uses glimpse_services.services.brightness, so a change to glimpse_services.services.brightness can break glimpse_services.services.exec, while a change to glimpse_services.services.exec can't break glimpse_services.services.brightness.
Position
Below the diagonal: glimpse_services.services.exec uses a module listed above it, which is the healthy direction.
23→24 glimpse_services.services.exec uses glimpse_services.subscriptionpart of a loop✕
Connections
1 pair of types, where a type in glimpse_services.services.exec uses a type in glimpse_services.subscription.
glimpse_services.services.exec uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.exec, while a change to glimpse_services.services.exec can't break glimpse_services.subscription.
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.
23→25 glimpse_services.services.exec uses glimpse_services.services.bluetoothpart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.exec uses a type in glimpse_services.services.bluetooth.
glimpse_services.services.exec uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.exec, while a change to glimpse_services.services.exec can't break glimpse_services.services.bluetooth.
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.
23→26 glimpse_services.services.exec uses glimpse_services.services.batterypart of a loop✕
Connections
1 pair of types, where a type in glimpse_services.services.exec uses a type in glimpse_services.services.battery.
glimpse_services.services.exec uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.exec, while a change to glimpse_services.services.exec can't break glimpse_services.services.battery.
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.
23→34 glimpse_services.services.exec uses glimpse_services.servicepart of a loop✕
Connections
3 pairs of types, where a type in glimpse_services.services.exec uses a type in glimpse_services.service.
glimpse_services.services.exec uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.exec, while a change to glimpse_services.services.exec can't break glimpse_services.service.
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.
glimpse_services.subscription uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.subscription, while a change to glimpse_services.subscription can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.subscription uses a module listed above it, which is the healthy direction.
glimpse_services.subscription uses glimpse_services.services.exec, so a change to glimpse_services.services.exec can break glimpse_services.subscription, while a change to glimpse_services.subscription can't break glimpse_services.services.exec.
Position
Below the diagonal: glimpse_services.subscription uses a module listed above it, which is the healthy direction.
24→28 glimpse_services.subscription uses glimpse_services.services.audio.pulsepart of a loop✕
Connections
1 pair of types, where a type in glimpse_services.subscription uses a type in glimpse_services.services.audio.pulse.
glimpse_services.subscription uses glimpse_services.services.audio.pulse, so a change to glimpse_services.services.audio.pulse can break glimpse_services.subscription, while a change to glimpse_services.subscription can't break glimpse_services.services.audio.pulse.
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.
glimpse_services.services.bluetooth uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.bluetooth, while a change to glimpse_services.services.bluetooth can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.bluetooth uses a module listed above it, which is the healthy direction.
glimpse_services.services.bluetooth uses glimpse_services.services.audio.model, so a change to glimpse_services.services.audio.model can break glimpse_services.services.bluetooth, while a change to glimpse_services.services.bluetooth can't break glimpse_services.services.audio.model.
Position
Below the diagonal: glimpse_services.services.bluetooth uses a module listed above it, which is the healthy direction.
glimpse_services.services.bluetooth uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.bluetooth, while a change to glimpse_services.services.bluetooth can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.bluetooth uses a module listed above it, which is the healthy direction.
glimpse_services.services.bluetooth uses glimpse_services.services.bluetooth.failure, so a change to glimpse_services.services.bluetooth.failure can break glimpse_services.services.bluetooth, while a change to glimpse_services.services.bluetooth can't break glimpse_services.services.bluetooth.failure.
Position
Below the diagonal: glimpse_services.services.bluetooth uses a module listed above it, which is the healthy direction.
glimpse_services.services.bluetooth uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.bluetooth, while a change to glimpse_services.services.bluetooth can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.bluetooth uses a module listed above it, which is the healthy direction.
25→26 glimpse_services.services.bluetooth uses glimpse_services.services.batterypart of a loop✕
Connections
1 pair of types, where a type in glimpse_services.services.bluetooth uses a type in glimpse_services.services.battery.
glimpse_services.services.bluetooth uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.bluetooth, while a change to glimpse_services.services.bluetooth can't break glimpse_services.services.battery.
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.
25→29 glimpse_services.services.bluetooth uses glimpse_services.services.audiopart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.bluetooth uses a type in glimpse_services.services.audio.
glimpse_services.services.bluetooth uses glimpse_services.services.audio, so a change to glimpse_services.services.audio can break glimpse_services.services.bluetooth, while a change to glimpse_services.services.bluetooth can't break glimpse_services.services.audio.
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.
25→34 glimpse_services.services.bluetooth uses glimpse_services.servicepart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.bluetooth uses a type in glimpse_services.service.
glimpse_services.services.bluetooth uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.bluetooth, while a change to glimpse_services.services.bluetooth can't break glimpse_services.service.
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.
glimpse_services.services.battery uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.battery, while a change to glimpse_services.services.battery can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.battery uses a module listed above it, which is the healthy direction.
glimpse_services.services.battery uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.battery, while a change to glimpse_services.services.battery can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.battery uses a module listed above it, which is the healthy direction.
glimpse_services.services.battery uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.battery, while a change to glimpse_services.services.battery can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.battery uses a module listed above it, which is the healthy direction.
glimpse_services.services.battery uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.battery, while a change to glimpse_services.services.battery can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.battery uses a module listed above it, which is the healthy direction.
26→34 glimpse_services.services.battery uses glimpse_services.servicepart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.battery uses a type in glimpse_services.service.
glimpse_services.services.battery uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.battery, while a change to glimpse_services.services.battery can't break glimpse_services.service.
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.
glimpse_services.services.removable uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.removable, while a change to glimpse_services.services.removable can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.removable uses a module listed above it, which is the healthy direction.
glimpse_services.services.removable uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.removable, while a change to glimpse_services.services.removable can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.removable uses a module listed above it, which is the healthy direction.
glimpse_services.services.removable uses glimpse_services.services.bluetooth.failure, so a change to glimpse_services.services.bluetooth.failure can break glimpse_services.services.removable, while a change to glimpse_services.services.removable can't break glimpse_services.services.bluetooth.failure.
Position
Below the diagonal: glimpse_services.services.removable uses a module listed above it, which is the healthy direction.
glimpse_services.services.removable uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.removable, while a change to glimpse_services.services.removable can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.removable uses a module listed above it, which is the healthy direction.
glimpse_services.services.removable uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.removable, while a change to glimpse_services.services.removable can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.removable uses a module listed above it, which is the healthy direction.
glimpse_services.services.removable uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.removable, while a change to glimpse_services.services.removable can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.services.removable uses a module listed above it, which is the healthy direction.
27→29 glimpse_services.services.removable uses glimpse_services.services.audiopart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.removable uses a type in glimpse_services.services.audio.
glimpse_services.services.removable uses glimpse_services.services.audio, so a change to glimpse_services.services.audio can break glimpse_services.services.removable, while a change to glimpse_services.services.removable can't break glimpse_services.services.audio.
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.
27→34 glimpse_services.services.removable uses glimpse_services.servicepart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.removable uses a type in glimpse_services.service.
glimpse_services.services.removable uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.removable, while a change to glimpse_services.services.removable can't break glimpse_services.service.
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.
glimpse_services.services.audio.pulse uses glimpse_services.services.audio.model, so a change to glimpse_services.services.audio.model can break glimpse_services.services.audio.pulse, while a change to glimpse_services.services.audio.pulse can't break glimpse_services.services.audio.model.
Position
Below the diagonal: glimpse_services.services.audio.pulse uses a module listed above it, which is the healthy direction.
glimpse_services.services.audio.pulse uses glimpse_services.services.removable, so a change to glimpse_services.services.removable can break glimpse_services.services.audio.pulse, while a change to glimpse_services.services.audio.pulse can't break glimpse_services.services.removable.
Position
Below the diagonal: glimpse_services.services.audio.pulse uses a module listed above it, which is the healthy direction.
glimpse_services.services.audio uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.audio, while a change to glimpse_services.services.audio can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.audio uses a module listed above it, which is the healthy direction.
glimpse_services.services.audio uses glimpse_services.services.audio.model, so a change to glimpse_services.services.audio.model can break glimpse_services.services.audio, while a change to glimpse_services.services.audio can't break glimpse_services.services.audio.model.
Position
Below the diagonal: glimpse_services.services.audio uses a module listed above it, which is the healthy direction.
glimpse_services.services.audio uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.audio, while a change to glimpse_services.services.audio can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.audio uses a module listed above it, which is the healthy direction.
glimpse_services.services.audio uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.audio, while a change to glimpse_services.services.audio can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.audio uses a module listed above it, which is the healthy direction.
glimpse_services.services.audio uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.audio, while a change to glimpse_services.services.audio can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.audio uses a module listed above it, which is the healthy direction.
glimpse_services.services.audio uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.audio, while a change to glimpse_services.services.audio can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.services.audio uses a module listed above it, which is the healthy direction.
glimpse_services.services.audio uses glimpse_services.services.audio.pulse, so a change to glimpse_services.services.audio.pulse can break glimpse_services.services.audio, while a change to glimpse_services.services.audio can't break glimpse_services.services.audio.pulse.
Position
Below the diagonal: glimpse_services.services.audio uses a module listed above it, which is the healthy direction.
29→34 glimpse_services.services.audio uses glimpse_services.servicepart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.audio uses a type in glimpse_services.service.
glimpse_services.services.audio uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.audio, while a change to glimpse_services.services.audio can't break glimpse_services.service.
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.
glimpse_services.services.compositor uses glimpse_compositors.model, so a change to glimpse_compositors.model can break glimpse_services.services.compositor, while a change to glimpse_services.services.compositor can't break glimpse_compositors.model.
Position
Below the diagonal: glimpse_services.services.compositor uses a module listed above it, which is the healthy direction.
glimpse_services.services.compositor uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.compositor, while a change to glimpse_services.services.compositor can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.compositor uses a module listed above it, which is the healthy direction.
glimpse_services.services.compositor uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.compositor, while a change to glimpse_services.services.compositor can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.compositor uses a module listed above it, which is the healthy direction.
glimpse_services.services.compositor uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.compositor, while a change to glimpse_services.services.compositor can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.compositor uses a module listed above it, which is the healthy direction.
glimpse_services.services.compositor uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.compositor, while a change to glimpse_services.services.compositor can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.compositor uses a module listed above it, which is the healthy direction.
glimpse_services.services.compositor uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.compositor, while a change to glimpse_services.services.compositor can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.services.compositor uses a module listed above it, which is the healthy direction.
glimpse_services.services.compositor uses glimpse_services.services.audio, so a change to glimpse_services.services.audio can break glimpse_services.services.compositor, while a change to glimpse_services.services.compositor can't break glimpse_services.services.audio.
Position
Below the diagonal: glimpse_services.services.compositor uses a module listed above it, which is the healthy direction.
30→34 glimpse_services.services.compositor uses glimpse_services.servicepart of a loop✕
Connections
3 pairs of types, where a type in glimpse_services.services.compositor uses a type in glimpse_services.service.
glimpse_services.services.compositor uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.compositor, while a change to glimpse_services.services.compositor can't break glimpse_services.service.
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.
glimpse_services.services.mpris uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.mpris uses a module listed above it, which is the healthy direction.
glimpse_services.services.mpris uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.mpris uses a module listed above it, which is the healthy direction.
glimpse_services.services.mpris uses glimpse_services.services.bluetooth.failure, so a change to glimpse_services.services.bluetooth.failure can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.services.bluetooth.failure.
Position
Below the diagonal: glimpse_services.services.mpris uses a module listed above it, which is the healthy direction.
glimpse_services.services.mpris uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.mpris uses a module listed above it, which is the healthy direction.
glimpse_services.services.mpris uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.mpris uses a module listed above it, which is the healthy direction.
glimpse_services.services.mpris uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.services.mpris uses a module listed above it, which is the healthy direction.
glimpse_services.services.mpris uses glimpse_services.services.audio.pulse, so a change to glimpse_services.services.audio.pulse can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.services.audio.pulse.
Position
Below the diagonal: glimpse_services.services.mpris uses a module listed above it, which is the healthy direction.
glimpse_services.services.mpris uses glimpse_services.services.audio, so a change to glimpse_services.services.audio can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.services.audio.
Position
Below the diagonal: glimpse_services.services.mpris uses a module listed above it, which is the healthy direction.
31→34 glimpse_services.services.mpris uses glimpse_services.servicepart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.mpris uses a type in glimpse_services.service.
glimpse_services.services.mpris uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.mpris, while a change to glimpse_services.services.mpris can't break glimpse_services.service.
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.
glimpse_services.services.network uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.network, while a change to glimpse_services.services.network can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.network uses a module listed above it, which is the healthy direction.
glimpse_services.services.network uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.network, while a change to glimpse_services.services.network can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.network uses a module listed above it, which is the healthy direction.
glimpse_services.services.network uses glimpse_services.services.bluetooth.failure, so a change to glimpse_services.services.bluetooth.failure can break glimpse_services.services.network, while a change to glimpse_services.services.network can't break glimpse_services.services.bluetooth.failure.
Position
Below the diagonal: glimpse_services.services.network uses a module listed above it, which is the healthy direction.
glimpse_services.services.network uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.network, while a change to glimpse_services.services.network can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.network uses a module listed above it, which is the healthy direction.
glimpse_services.services.network uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.network, while a change to glimpse_services.services.network can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.network uses a module listed above it, which is the healthy direction.
glimpse_services.services.network uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.network, while a change to glimpse_services.services.network can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.services.network uses a module listed above it, which is the healthy direction.
glimpse_services.services.network uses glimpse_services.services.audio, so a change to glimpse_services.services.audio can break glimpse_services.services.network, while a change to glimpse_services.services.network can't break glimpse_services.services.audio.
Position
Below the diagonal: glimpse_services.services.network uses a module listed above it, which is the healthy direction.
32→34 glimpse_services.services.network uses glimpse_services.servicepart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.network uses a type in glimpse_services.service.
glimpse_services.services.network uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.network, while a change to glimpse_services.services.network can't break glimpse_services.service.
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.
glimpse_services.services.keyboard uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.keyboard, while a change to glimpse_services.services.keyboard can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.keyboard uses a module listed above it, which is the healthy direction.
glimpse_services.services.keyboard uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.keyboard, while a change to glimpse_services.services.keyboard can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.keyboard uses a module listed above it, which is the healthy direction.
glimpse_services.services.keyboard uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.keyboard, while a change to glimpse_services.services.keyboard can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.keyboard uses a module listed above it, which is the healthy direction.
glimpse_services.services.keyboard uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.keyboard, while a change to glimpse_services.services.keyboard can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.keyboard uses a module listed above it, which is the healthy direction.
glimpse_services.services.keyboard uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.keyboard, while a change to glimpse_services.services.keyboard can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.services.keyboard uses a module listed above it, which is the healthy direction.
glimpse_services.services.keyboard uses glimpse_services.services.compositor, so a change to glimpse_services.services.compositor can break glimpse_services.services.keyboard, while a change to glimpse_services.services.keyboard can't break glimpse_services.services.compositor.
Position
Below the diagonal: glimpse_services.services.keyboard uses a module listed above it, which is the healthy direction.
33→34 glimpse_services.services.keyboard uses glimpse_services.servicepart of a loop✕
Connections
2 pairs of types, where a type in glimpse_services.services.keyboard uses a type in glimpse_services.service.
glimpse_services.services.keyboard uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.keyboard, while a change to glimpse_services.services.keyboard can't break glimpse_services.service.
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.
glimpse_services.service uses glimpse_services.services.audio.model, so a change to glimpse_services.services.audio.model can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.audio.model.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_dbus.clients.weather, so a change to glimpse_dbus.clients.weather can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_dbus.clients.weather.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.bluetooth.failure, so a change to glimpse_services.services.bluetooth.failure can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.bluetooth.failure.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.exec, so a change to glimpse_services.services.exec can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.exec.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.removable, so a change to glimpse_services.services.removable can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.removable.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.audio, so a change to glimpse_services.services.audio can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.audio.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.compositor, so a change to glimpse_services.services.compositor can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.compositor.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.mpris, so a change to glimpse_services.services.mpris can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.mpris.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.network, so a change to glimpse_services.services.network can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.network.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_services.service uses glimpse_services.services.keyboard, so a change to glimpse_services.services.keyboard can break glimpse_services.service, while a change to glimpse_services.service can't break glimpse_services.services.keyboard.
Position
Below the diagonal: glimpse_services.service uses a module listed above it, which is the healthy direction.
glimpse_notifications.app uses glimpse_compositors.model, so a change to glimpse_compositors.model can break glimpse_notifications.app, while a change to glimpse_notifications.app can't break glimpse_compositors.model.
Position
Below the diagonal: glimpse_notifications.app uses a module listed above it, which is the healthy direction.
glimpse_notifications.app uses glimpse_config.schema, so a change to glimpse_config.schema can break glimpse_notifications.app, while a change to glimpse_notifications.app can't break glimpse_config.schema.
Position
Below the diagonal: glimpse_notifications.app uses a module listed above it, which is the healthy direction.
glimpse_notifications.app uses glimpse_services.services.compositor, so a change to glimpse_services.services.compositor can break glimpse_notifications.app, while a change to glimpse_notifications.app can't break glimpse_services.services.compositor.
Position
Below the diagonal: glimpse_notifications.app uses a module listed above it, which is the healthy direction.
glimpse_notifications.app uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_notifications.app, while a change to glimpse_notifications.app can't break glimpse_services.service.
Position
Below the diagonal: glimpse_notifications.app uses a module listed above it, which is the healthy direction.
glimpse_panel.applet uses glimpse_widgets.indicator, so a change to glimpse_widgets.indicator can break glimpse_panel.applet, while a change to glimpse_panel.applet can't break glimpse_widgets.indicator.
Position
Below the diagonal: glimpse_panel.applet uses a module listed above it, which is the healthy direction.
glimpse_panel.applet uses glimpse_panel.applet.popover, so a change to glimpse_panel.applet.popover can break glimpse_panel.applet, while a change to glimpse_panel.applet can't break glimpse_panel.applet.popover.
Position
Below the diagonal: glimpse_panel.applet uses a module listed above it, which is the healthy direction.
glimpse_panel.applet uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_panel.applet, while a change to glimpse_panel.applet can't break glimpse_services.service.
Position
Below the diagonal: glimpse_panel.applet uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_compositors.contract, so a change to glimpse_compositors.contract can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_compositors.contract.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_services.services.audio.model, so a change to glimpse_services.services.audio.model can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_services.services.audio.model.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_services.services.audio, so a change to glimpse_services.services.audio can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_services.services.audio.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.kdeconnect uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.kdeconnect, while a change to glimpse_services.services.kdeconnect can't break glimpse_services.service.
Position
Below the diagonal: glimpse_services.services.kdeconnect uses a module listed above it, which is the healthy direction.
glimpse_services.services.weather uses glimpse_services.publisher, so a change to glimpse_services.publisher can break glimpse_services.services.weather, while a change to glimpse_services.services.weather can't break glimpse_services.publisher.
Position
Below the diagonal: glimpse_services.services.weather uses a module listed above it, which is the healthy direction.
glimpse_services.services.weather uses glimpse_dbus.clients.weather, so a change to glimpse_dbus.clients.weather can break glimpse_services.services.weather, while a change to glimpse_services.services.weather can't break glimpse_dbus.clients.weather.
Position
Below the diagonal: glimpse_services.services.weather uses a module listed above it, which is the healthy direction.
glimpse_services.services.weather uses glimpse_services.context, so a change to glimpse_services.context can break glimpse_services.services.weather, while a change to glimpse_services.services.weather can't break glimpse_services.context.
Position
Below the diagonal: glimpse_services.services.weather uses a module listed above it, which is the healthy direction.
glimpse_services.services.weather uses glimpse_services.subscription, so a change to glimpse_services.subscription can break glimpse_services.services.weather, while a change to glimpse_services.services.weather can't break glimpse_services.subscription.
Position
Below the diagonal: glimpse_services.services.weather uses a module listed above it, which is the healthy direction.
glimpse_services.services.weather uses glimpse_services.services.bluetooth, so a change to glimpse_services.services.bluetooth can break glimpse_services.services.weather, while a change to glimpse_services.services.weather can't break glimpse_services.services.bluetooth.
Position
Below the diagonal: glimpse_services.services.weather uses a module listed above it, which is the healthy direction.
glimpse_services.services.weather uses glimpse_services.services.battery, so a change to glimpse_services.services.battery can break glimpse_services.services.weather, while a change to glimpse_services.services.weather can't break glimpse_services.services.battery.
Position
Below the diagonal: glimpse_services.services.weather uses a module listed above it, which is the healthy direction.
glimpse_services.services.weather uses glimpse_services.services.audio.pulse, so a change to glimpse_services.services.audio.pulse can break glimpse_services.services.weather, while a change to glimpse_services.services.weather can't break glimpse_services.services.audio.pulse.
Position
Below the diagonal: glimpse_services.services.weather uses a module listed above it, which is the healthy direction.
glimpse_services.services.weather uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_services.services.weather, while a change to glimpse_services.services.weather can't break glimpse_services.service.
Position
Below the diagonal: glimpse_services.services.weather uses a module listed above it, which is the healthy direction.
glimpse_lock.app uses glimpse_config.schema, so a change to glimpse_config.schema can break glimpse_lock.app, while a change to glimpse_lock.app can't break glimpse_config.schema.
Position
Below the diagonal: glimpse_lock.app uses a module listed above it, which is the healthy direction.
glimpse_lock.app uses glimpse_services.services.compositor, so a change to glimpse_services.services.compositor can break glimpse_lock.app, while a change to glimpse_lock.app can't break glimpse_services.services.compositor.
Position
Below the diagonal: glimpse_lock.app uses a module listed above it, which is the healthy direction.
glimpse_lock.app uses glimpse_services.services.mpris, so a change to glimpse_services.services.mpris can break glimpse_lock.app, while a change to glimpse_lock.app can't break glimpse_services.services.mpris.
Position
Below the diagonal: glimpse_lock.app uses a module listed above it, which is the healthy direction.
glimpse_lock.app uses glimpse_services.service, so a change to glimpse_services.service can break glimpse_lock.app, while a change to glimpse_lock.app can't break glimpse_services.service.
Position
Below the diagonal: glimpse_lock.app uses a module listed above it, which is the healthy direction.
glimpse_lock.app uses glimpse_services.services.weather, so a change to glimpse_services.services.weather can break glimpse_lock.app, while a change to glimpse_lock.app can't break glimpse_services.services.weather.
Position
Below the diagonal: glimpse_lock.app uses a module listed above it, which is the healthy direction.
glimpse_panel.components.panel uses glimpse_compositors.model, so a change to glimpse_compositors.model can break glimpse_panel.components.panel, while a change to glimpse_panel.components.panel can't break glimpse_compositors.model.
Position
Below the diagonal: glimpse_panel.components.panel uses a module listed above it, which is the healthy direction.
glimpse_panel.components.panel uses glimpse_panel.applet, so a change to glimpse_panel.applet can break glimpse_panel.components.panel, while a change to glimpse_panel.components.panel can't break glimpse_panel.applet.
Position
Below the diagonal: glimpse_panel.components.panel 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
52
High / Critical
A03:2025 — Software Supply Chain Failures
19
High / Critical
Roadmap
Top priorities: Thread a context.Context through functions that make requests, so the work stops when its caller gives up; Enable Dependabot/Renovate or a dependency-review gate; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Exec::handle (cyclomatic 124), Dom::dress (cyclomatic 111), glimpsectl::commands::run::applets_run (cyclomatic 66).
Use the awaited twin of each blocking call, or move the work off the loop with `tokio::task::spawn_blocking` — a synchronous handler cannot simply `.await` in place.
Code Duplication: Edited copy of a member (7 corresponding lines)
crates/glimpse-widgets/src/idle_popover/imp.rs
5.9
Mixed
Code Duplication: Edited copy of a member (7 corresponding lines)
crates/glimpse-widgets/src/shot_toolbar/imp.rs
6.3
Mixed
God Classes: TooManyFields: ShotToolbar
crates/glimpse-widgets/src/lock_stage/imp.rs
6.3
Mixed
God Classes: TooManyMethods: LockStage
crates/glimpse-widgets/src/clipboard_list/imp.rs
6.3
Mixed
Code Duplication: Edited copy of a member (16 corresponding lines)
crates/glimpse-widgets/src/calendar/imp.rs
6.3
Mixed
Code Duplication: Edited copy of a member (13 corresponding lines)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 77
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 — 824
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 — 108
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 73 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 73 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, 973 of 1009 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 14 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 192 test source file(s) (.rs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the node:test run in sdk/sdk-ts/ produced no per-test report (> glimpse-sdk@0.13.1 test). This is OUR limitation, not a defect in the repo — it is excluded from the score.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the node:test suite in sdk/sdk-ts/ was NOT MEASURED: the node:test run in sdk/sdk-ts/ produced no per-test report (> glimpse-sdk@0.13.1 test). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 1589 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `sdk/sdk-py/glimpse_sdk/applet.py`, `sdk/sdk-py/glimpse_sdk/context.py`, `sdk/sdk-py/glimpse_sdk/runtime.py`, `sdk/sdk-py/glimpse_sdk/session.py`, `sdk/sdk-py/glimpse_sdk/widget.py`, … (+1 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run dev` in website/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / llmstxt » Dev server configured for serving plain text docs for LLMs / llmstxt » Build started, file collection cleared / vitepress v1.6.4 / ➜ Local: http://localhost:5173/glimpse/ / ➜ Network: use --host to expose" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev` in website/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / llmstxt » Dev server configured for serving plain text docs for LLMs / llmstxt » Build started, file collection cleared / vitepress v1.6.4 / ➜ Local: http://localhost:5173/glimpse/ / ➜ Network: use --host to expose" No runtime evidence was gathered.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X17 Uncapped recursion over a caller-supplied document — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 26 further occurrence(s) are not listed individually; the score already reflects all 66.
X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
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 (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
65 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Exec::handle at 124. A further 22 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 glimpsectl::run at 58 — they are counted neither in the figure above nor in this dimension's score. 16 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/glimpsectl/src/main.rs (glimpsectl::run at 58), crates/glimpse-services/src/services/exec/tree.rs (ElementKind::name at 41), crates/glimpse-dbus/src/clients/udisks2.rs (Media::parse at 34), crates/glimpse-dbus/src/clients/upower.rs (DeviceKind::from_code at 29), crates/glimpse-panel/src/applets/mod.rs (glimpse_panel::applets::build at 25), and 11 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.
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Exec::handle (cyclomatic 124), Dom::dress (cyclomatic 111), glimpsectl::commands::run::applets_run (cyclomatic 66). — 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 4 together lifts Cyclomatic Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
+ 53 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with Exec::handle (cognitive 230), Dom::dress (cognitive 160), glimpsectl::commands::run::applets_run (cognitive 142). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 5.1 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 33 FileTooLong finding(s) in God Classes — start with mod.rs (6), app.rs (4), cli.rs (2). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 20 MethodTooLong finding(s) in God Classes — start with mod.rs (5), indicator.rs (5), dom.rs (2). — One of this dimension's main actionable groups (20 warning-level).
Resolve the 11 FunctionTooLong finding(s) in God Classes — start with run.rs, mod.rs, idle.rs. — One of this dimension's main actionable groups (11 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
167 duplicated block group(s) detected. 3.9 % of the production lines (7,813 of 201,071) are in a reported copy. A further 171 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 338 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (7 corresponding lines) · ×16crates/glimpse-widgets/src/hero/imp.rs:48
+ 95 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 24 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with imp.rs (5), mod.rs (4), indicator.rs (3). — One of this dimension's main actionable groups (24 warning-level).
Resolve the 18 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with mod.rs (6), imp.rs (2), outputs.rs. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 18 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with imp.rs (8), mod.rs (2), main.rs. — One of this dimension's main actionable groups (18 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.8 / 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.
27 production modules (Cargo+npm+Go+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 4 module(s) off the main sequence, with abstractness counted on 26 of the 27 (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: glimpse-config · ×4
What to do
Resolve the 4 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 46 Low cohesion finding(s) in Cohesion (LCOM4) — start with imp.rs (39), sparkline.rs, bars.rs. — One of this dimension's main actionable groups (46 warning-level).
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).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 14 tests. Measured on the JavaScript/TypeScript suite only — at least 192 test source file(s) (.rs) went unread, so its test quality is unmeasured and is not in these counts.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
24 outdated, 0 yanked direct Cargo dependencies. 65 of 66 direct crates were graded against crates.io (0 not published there, 1 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: ammonia · ×24
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 521 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under BSD-3-Clause, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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.
Resolve the 26 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (7), app.rs (4), dom.rs. — One of this dimension's main actionable groups (26 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
0 deducted task-comment markers across 201071 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 33 document(s) read across 30 unit(s).
Documentation: no build, run or usage example · ×17crates/glimpse-agents/README.md:1
What to do
Resolve the 17 Documentation finding(s) in Documentation Quality — start with README.md (17). — One of this dimension's main actionable groups (17 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
0 of 3 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
4 of 29 build units (Cargo, Go, Python, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×4crates/glimpse-widgets/Cargo.toml:1
What to do
Resolve the 4 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with Cargo.toml (4). — One of this dimension's main actionable groups (4 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).
52 finding(s): 0 critical, 51 high, 1 medium, 0 low. 49 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 19 file(s) — `crates/glimpse-panel/src/applets/weather/render.rs` (line 202), `scripts/build-binaries.sh` (line 4), `scripts/check-units.sh` (line 4), `scripts/docs-gen-cli.sh` (line 4), `scripts/exec-applet-demo.sh` (line 13), … (+14 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.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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).
No action in Static Analysis (SAST) — all 49 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (49 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 5 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 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.
1 of 661 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/glimpsectl/src/commands/applets/tests.rs. Counted over 661 of the 958 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 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.
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-Driven — Whether event/message handlers avoid synchronous blocking waits — a blocking wait inside a handler stalls throughput and risks deadlock.
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
`watch.inode` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-config/src/watch.rs:500
`clipboard.copy` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-lens/src/clipboard.rs:15
`probe.pam_stack` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-lock/src/probe.rs:201
`probe.shadow_mode` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-lock/src/probe.rs:262
`probe.own_chkpwd` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-lock/src/probe.rs:284
`probe.read` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-lock/src/probe.rs:298
`user.current` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-lock/src/user.rs:25
`spawn.unlink_if_ours` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-services/src/services/exec/spawn.rs:92
`spawn.unlink_if_ours` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::remove_file`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-services/src/services/exec/spawn.rs:93
`SlotStream.start` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-services/src/services/exec/spawn.rs:411
`CameraSource.rearm` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_dir`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-services/src/services/privacy/source.rs:133
`screens.connect` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-shot/src/adapters/screens.rs:69
`raster.store` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::rename`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-widgets/src/raster.rs:402
`raster.store` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::remove_file`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-widgets/src/raster.rs:404
`raster.evict` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_dir`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-widgets/src/raster.rs:435
`raster.evict` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpse-widgets/src/raster.rs:439
`raster.evict` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::remove_file`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×2) — crates/glimpse-widgets/src/raster.rs:457, crates/glimpse-widgets/src/raster.rs:469
`Scratch.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpsectl/src/commands/dev.rs:26
`OwnedPanel.start_with` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::write`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. (×2) — crates/glimpsectl/src/commands/dev.rs:125, crates/glimpsectl/src/commands/dev.rs:129
`run.locate` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_dir`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpsectl/src/commands/run.rs:30
`run.settings` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — crates/glimpsectl/src/commands/run.rs:59
`run.run_inner` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `recv`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`. — sdk/sdk-rs/src/run.rs:63
What to do
Use the awaited twin of each blocking call, or move the work off the loop with `tokio::task::spawn_blocking` — a synchronous handler cannot simply `.await` in place.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
`Keyboard.restore` performs two independent DURABLE writes — a durable state write (`store.remove`, :315) and an independent publish to an event bus (`events.send`, :338) — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox). — crates/glimpse-services/src/services/keyboard.rs:304
What to do
Adopt the transactional outbox pattern so DB writes and message publishes commit atomically — no lost or phantom events on a crash.
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.
Other · Code Health — Unreviewed-generation residue in this repository's Rust: functions whose whole body is still `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Rust: functions whose body is `todo!()`/`unimplemented!()` or only panics with a "not implemented" message, match arms and branches left as `todo!()`, functions that take inputs and return a constant (`Ok(())`, `None`, `Default::default()`, an empty `Vec`) or do nothing, and impls most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`withdraw_device` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-agents/src/bluetooth/mod.rs:306
`cancel_get_secrets` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-agents/src/network/mod.rs:252
`cancel_authentication` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-agents/src/polkit/agent.rs:290
`refuse` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-agents/src/queue.rs:58
`init` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-config/src/load.rs:82
`attention_accessible_desc` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-dbus/src/testing/tray.rs:216
`x_ayatana_label_guide` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-dbus/src/testing/tray.rs:236
`x_ayatana_ordering_index` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-dbus/src/testing/tray.rs:241
`attention_icon_pixmap` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-dbus/src/testing/tray.rs:342
`attention_movie_name` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-dbus/src/testing/tray.rs:347
`item_is_menu` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-dbus/src/testing/tray.rs:352
`send` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-idle/src/idle.rs:98
`query_end_response` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-idle/src/inhibitors/portal.rs:173
`close` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-idle/src/inhibitors/portal.rs:199
`ended` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-lock/src/logind.rs:397
`typing` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-panel/src/applet/mod.rs:254
`impl AppletHandle` has 4 unfinished methods out of 5 — a scaffolded type that was never implemented. — crates/glimpse-panel/src/applet/runtime.rs:669
`configure` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-panel/src/applet/runtime.rs:697
`set_orientation` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-panel/src/applet/runtime.rs:704
`set_slot` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-panel/src/applet/runtime.rs:711
`set_placement` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-panel/src/applet/runtime.rs:715
`entry_of` does real work, but one of its branches is `Err` with a "not implemented" message — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled. — crates/glimpse-services/src/services/exec/catalog.rs:138
`close_notification` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-services/src/services/notifications.rs:947
`announce` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-services/src/services/tray/watcher.rs:34
`protocol_version` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. (×2) — crates/glimpse-services/src/services/tray/watcher.rs:116, crates/glimpse-services/src/services/tray/watcher.rs:203
`register_status_notifier_host` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-services/src/services/tray/watcher.rs:182
`unexport` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-shot/src/portal.rs:547
`print` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — crates/glimpse-shot/src/prime.rs:5
`event` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-wayland/src/selection/protocol.rs:103
`touch` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — crates/glimpse-widgets/src/raster.rs:357
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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.
`sdk/examples/todo/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — sdk/examples/todo/package.json:5
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 · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
sdk/sdk-ts/testing.ts:108 · sdk/sdk-ts/testing.ts:134 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — sdk/sdk-ts/testing.ts:108
sdk/sdk-ts/testing.ts:97 · sdk/sdk-ts/testing.ts:112 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — sdk/sdk-ts/testing.ts:97
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
session has cyclomatic complexity 29 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sdk/sdk-ts/session.ts:129
commit has cyclomatic complexity 24 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sdk/sdk-ts/testing.ts:68
wireProps has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sdk/sdk-ts/wire.ts:107
dispatchEvent has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — sdk/sdk-ts/session.ts:85
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
Do you agree with this assessment?
R4 · Test Coverage10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
`widget.unparent();` follows `exit(& widget);` (line 53) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — crates/glimpse-widgets/src/reconcile.rs:54
`if ! sides.contains(& width) || ! sides.contains(& height) { return None; }` follows `{ return None; }` (line 1122) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run. — crates/glimpse-services/src/services/notifications.rs:1125
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
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 · 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 document1.1 / 10Critical✓ Tool-verified
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.
`oversized` is exported and takes `value: unknown` from its caller, and it calls itself at line 193 (`oversized`) with a piece of `value` (and at line 196) — and nowhere in `oversized` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `oversized` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — sdk/sdk-ts/wire.ts:193
`oversized` is public and takes `value: &Value` from its caller, and it calls itself at line 73 with a piece of the document (and at line 75) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `oversized` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — sdk/sdk-rs/src/protocol.rs:73
`set_workspaces` is public and takes a `WorkspacesPopover` as its receiver from its caller, and it calls itself at line 33 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_workspaces` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/workspaces_popover/mod.rs:33
`connect_activated` is public and takes a `WorkspacesPopover` as its receiver from its caller, and it calls itself at line 105 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `connect_activated` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/workspaces_popover/mod.rs:105
`set_workspaces` is public and takes a `WorkspaceList` as its receiver from its caller, and it recurses at line 63 through `render` and back with a piece of the document (and at line 113) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_workspaces` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/workspace_list/mod.rs:63
`holders` is public and takes a `WorkspaceList` as its receiver from its caller, and it calls itself at line 89 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `holders` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/workspace_list/mod.rs:89
`set_unit` is public and takes a `WeatherPopover` as its receiver from its caller, and it calls itself at line 69 with a piece of the document (and at line 70) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_unit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/weather_popover/mod.rs:69
`set_hours` is public and takes a `WeatherPopover` as its receiver from its caller, and it calls itself at line 75 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_hours` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/weather_popover/mod.rs:75
`set_days` is public and takes a `WeatherPopover` as its receiver from its caller, and it calls itself at line 81 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_days` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/weather_popover/mod.rs:81
`set_orientation` is public and takes a `TrayStrip` as its receiver from its caller, and it calls itself at line 67 with a piece of the document (and at line 76) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_orientation` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/tray_strip/mod.rs:67
`activate_from_user` is public, takes a document from its caller (line 107) and hands it to `apply_active`, which recurses at line 154 through `set_active` and back with a piece of the document (and at line 131) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `apply_active` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/toggle_row/imp.rs:154
`finish_drag` is public, takes a document from its caller (line 202) and hands it to `value`, which calls itself at line 61 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/slider_row/imp.rs:61
`constructed` is public, takes a document from its caller (line 243) and hands it to `set_value`, which calls itself at line 76 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/slider_row/imp.rs:76
`set_menu_model` is public and takes a `ShotResultPage` as its receiver from its caller, and it calls itself at line 108 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_menu_model` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/shot_result_page/mod.rs:108
`add_toast` is public and takes a `ShotResultPage` as its receiver from its caller, and it calls itself at line 143 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `add_toast` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/shot_result_page/mod.rs:143
`has_actions` is public and takes a `SessionSheet` as its receiver from its caller, and it calls itself at line 82 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `has_actions` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/session_sheet/mod.rs:82
`set_start` is public and takes a `Row` as its receiver from its caller, and it calls itself at line 27 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_start` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/row/mod.rs:27
`clear_start` is public and takes a `Row` as its receiver from its caller, and it calls itself at line 31 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `clear_start` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/row/mod.rs:31
`set_end` is public and takes a `Row` as its receiver from its caller, and it calls itself at line 35 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_end` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/row/mod.rs:35
`constructed` is public, takes a document from its caller (line 113) and hands it to `set_size`, which calls itself at line 86 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_size` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/popover_shell/imp.rs:86
`measure` is public and takes a `PopoverShell` as its receiver from its caller, and it calls itself at line 173 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `measure` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/popover_shell/imp.rs:173
`set_title` is public and takes a `PlayerRow` as its receiver from its caller, and it calls itself at line 103 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_title` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/player_list/row.rs:103
`set_subtitle` is public and takes a `PlayerRow` as its receiver from its caller, and it calls itself at line 110 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_subtitle` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/player_list/row.rs:110
`set_icon_name` is public and takes a `PlayerRow` as its receiver from its caller, and it calls itself at line 117 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_icon_name` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/player_list/row.rs:117
`grab_focus` is public and takes a `PasswordPrompt` as its receiver from its caller, and it calls itself at line 132 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `grab_focus` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/password_prompt/imp.rs:132
`submit` is public and takes a `PasswordPrompt` as its receiver from its caller, and it calls itself at line 75 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `submit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/password_prompt/mod.rs:75
`set_orientation` is public and takes a `Panel` as its receiver from its caller, and it calls itself at line 51 with a piece of the document (and at line 53) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_orientation` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/panel/mod.rs:51
`set_orientation` is public and takes a `Pager` as its receiver from its caller, and it calls itself at line 65 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_orientation` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/pager/mod.rs:65
`constructed` is public, takes a document from its caller (line 140) and hands it to `sync`, which recurses at line 86 through `set_label`, `set_icon_name` and back with a piece of the document (and at line 41, line 51, line 113) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `sync` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/osd_view/imp.rs:86
`set_art` is public, takes a document from its caller (line 108) and hands it to `set_icon_name`, which calls itself at line 55 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_icon_name` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/now_playing/imp.rs:55
`set_art` is public and takes a `NowPlaying` as its receiver from its caller, and it calls itself at line 33 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_art` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/now_playing/mod.rs:33
`set_app_icon` is public and takes a `NotificationCard` as its receiver from its caller, and it calls itself at line 63 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_app_icon` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/notification_card/mod.rs:63
`set_image` is public and takes a `NotificationCard` as its receiver from its caller, and it calls itself at line 67 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_image` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/notification_card/mod.rs:67
`set_controls_visible` is public and takes a `NotificationCard` as its receiver from its caller, and it calls itself at line 116 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_controls_visible` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/notification_card/mod.rs:116
`set_awake` is public and takes a `LockStage` as its receiver from its caller, and it recurses at line 194 through `cover_when_idle`, `arm_cover`, `touch` and back with a piece of the document (and at line 247, line 260, line 274, line 277, line 278) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_awake` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/lock_stage/imp.rs:194
`set_awake` is public and takes a `LockStage` as its receiver from its caller, and it calls itself at line 83 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_awake` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/lock_stage/mod.rs:83
`set_interactive` is public and takes a `LockStage` as its receiver from its caller, and it calls itself at line 76 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_interactive` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/lock_stage/mod.rs:76
`set_user` is public and takes a `LockStage` as its receiver from its caller, and it calls itself at line 96 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_user` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/lock_stage/mod.rs:96
`set_message` is public and takes a `LockStage` as its receiver from its caller, and it calls itself at line 111 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_message` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/lock_stage/mod.rs:111
`set_busy` is public and takes a `LockStage` as its receiver from its caller, and it calls itself at line 125 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_busy` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — crates/glimpse-widgets/src/lock_stage/mod.rs:125
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
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.
`session` (line 56) is a `Session` this function owns and never releases: no `close()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Session` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends. — sdk/sdk-rs/src/run.rs:56
`section` (line 88) is a `Section` this function owns and never releases: no `print()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Section` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends. — crates/glimpsectl/src/commands/doctor.rs:88
`section` (line 144) is a `Section` this function owns and never releases: no `print()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Section` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends. — crates/glimpsectl/src/commands/doctor.rs:144
`section` (line 142) is a `Section` this function owns and never releases: no `print()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Section` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends. — crates/glimpse-widgets/src/notifications_popover/mod.rs:142
`section` (line 495) is a `Section` this function owns and never releases: no `print()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Section` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends. — crates/glimpse-panel/src/applets/exec/dom.rs:495
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether functions that make a cancellable request accept or pass on a context.Context (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/1 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`run` calls `net.Dial(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — sdk/sdk-go/sdk/run.go:32
What to do
Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`. In Rust, where a guard or permit releases when it is dropped, whether a release written BY HAND — `add_permits` after a forgotten permit, `force_unlock` after a leaked guard, a raw lock's `unlock` — matches the state the function's own acquisitions put the primitive in: not after a try or timed acquire whose failure does not leave, not from a cleanup set up before an acquire that can fail, not skipped by a `?`, `return`, `break` or `continue`, and not on top of a guard that still releases itself.
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.
`tracing::debug!` at line 254 is called with an argument built by `self.applets.iter().filter(|slot|slot.handle.is_some()).count()` (line 258), whose cost grows with the collection it walks. Rust evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because tracing::debug! is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `log_enabled!`/`tracing::enabled!` test, no debug flag, no `cfg(debug_assertions)`, and the work is in the argument itself, not deferred into a field the subscriber formats or a closure the formatter calls. — crates/glimpse-panel/src/components/panel.rs:254
What to do
In Rust, hand the logger the value and let it format only what it writes: `debug!("rows: {:?}", rows)` or a field, `debug!(rows = ?rows, "loaded")` — `format_args!` and `?`/`%` fields defer the formatting. When the line needs a computed view (a `collect`, a `join`, a `serde_json::to_string`), put it behind `if log_enabled!(Level::Debug)` (`if tracing::enabled!(Level::DEBUG)` for tracing), which asks the target's own filter. The macros put their arguments behind the global maximum level only, so a collect or serialisation in the argument runs whenever any target is at debug, and the logger then drops this line.
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.
`SliderRowProps.on_move` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:432
`SliderRowProps.on_change` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:433
`EntryProps.on_change` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:460
`EntryProps.on_submit` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:461
`EntryRowProps.on_change` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:473
`EntryRowProps.on_submit` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:474
`ScaleProps.on_change` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:575
`ChoiceListProps.on_select` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:641
`CalendarProps.on_month` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:679
`CalendarProps.on_select` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:680
`DropDownProps.on_select` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpse-services/src/services/exec/tree.rs:689
`IdleCommand::Inhibit.lapse` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing. — crates/glimpsectl/src/cli.rs:209
What to do
Each finding names the spans that disagree — the knob the caller supplies and the site that ignores it, whether by re-spelling its default, by falling back under the wrong key, by parsing with no format provider at all, or by printing under whatever culture the host supplies. Confirm from those spans, then decide which of the two the type meant: read the knob at the named site, or drop the knob so the signature stops advertising something the type cannot feel. Leaving both is the one option that cannot be right.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for … range` leaves the slice or map it is walking alone — Go raises nothing, but the walk and the collection part: a range evaluates its slice once, so an element appended in the body is never visited and a removal by reslicing (`s = append(s[:i], s[i+1:]...)`, `slices.Delete`) shifts the next element under the index, which is then skipped while the last is read twice; a reslice, a reassignment or a sort leaves every later `s[i]` naming another element; and a map's order is unspecified, so deleting another key (or clearing the map) changes from run to run which entries the loop still sees.
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.
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.
`error!` at line 24 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/glimpse-weather/src/main.rs:24
`error!` at line 20 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/glimpse-wallpaper/src/main.rs:20
`warn!` 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: `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/glimpse-wallpaper/src/surface.rs:301
`error!` at line 26 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`. (×2) — crates/glimpse-sunset/src/main.rs:26, crates/glimpse-settings-daemon/src/main.rs:26
`warn!` at line 327 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/glimpse-shot/src/headless.rs:327
`warn!` at line 132 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/glimpse-shot/src/hold.rs:132
`warn!` at line 128 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/glimpse-shot/src/main.rs:128
`warn!` at line 63 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/glimpse-shot/src/notify.rs:63
`warn!` at line 184 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/glimpse-shot/src/notify.rs:184
`warn!` at line 107 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/glimpse-shot/src/gui/app.rs:107
`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/glimpse-shot/src/gui/app.rs:163
`debug!` at line 180 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/glimpse-shot/src/gui/app.rs:180
`warn!` at line 434 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/glimpse-shot/src/gui/app.rs:434
`warn!` at line 442 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/glimpse-shot/src/gui/app.rs:442
`warn!` at line 1116 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/glimpse-shot/src/gui/app.rs:1116
`warn!` at line 39 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/glimpse-shot/src/gui/mod.rs:39
`warn!` at line 268 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/glimpse-shot/src/gui/overlay.rs:268
`warn!` at line 1419 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/glimpse-shot/src/gui/overlay.rs:1419
`warn!` at line 246 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/glimpse-shot/src/gui/prefs.rs:246
`warn!` at line 290 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/glimpse-shot/src/gui/prefs.rs:290
`warn!` at line 294 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/glimpse-shot/src/gui/prefs.rs:294
`warn!` at line 498 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/glimpse-shot/src/gui/result.rs:498
`warn!` at line 508 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/glimpse-shot/src/gui/result.rs:508
`warn!` at line 1142 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/glimpse-shot/src/gui/result.rs:1142
`debug!` at line 1216 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/glimpse-shot/src/gui/result.rs:1216
`warn!` at line 1229 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/glimpse-shot/src/gui/result.rs:1229
`warn!` at line 114 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/glimpse-shot/src/adapters/windows.rs:114
`warn!` at line 123 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/glimpse-shot/src/adapters/windows.rs:123
`warn!` 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: `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/glimpse-shot/src/adapters/windows.rs:133
`warn!` at line 37 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/glimpse-services/src/services/weather/met_no.rs:37
`error!` at line 28 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/glimpse-panel/src/main.rs:28
`debug!` at line 40 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/glimpse-panel/src/osd.rs:40
`debug!` at line 107 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/glimpse-panel/src/osd.rs:107
`warn!` at line 332 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/glimpse-panel/src/applets/clipboard/indicator.rs:332
`error!` at line 22 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/glimpse-notifications/src/main.rs:22
`warn!` at line 853 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/glimpse-lock/src/app.rs:853
`debug!` at line 937 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/glimpse-lock/src/app.rs:937
`warn!` at line 1184 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/glimpse-lock/src/app.rs:1184
`error!` at line 65 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/glimpse-lock/src/logind.rs:65
Other · Code Health — Whether Rust's absent values are handled rather than forced — `Option` and `Result` make absence a value the caller must handle in every crate, and each `.unwrap()` or `.expect()` that no guard on its path proves present is a panic the first time the value is `None` or `Err`.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
`std::fs::create_dir_all(parent)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_blueprints` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/build.rs:5
`std::process::Command::new("blueprint-compiler").args(["compile",src]).output()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `compile_blueprints` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/build.rs:10
`std::fs::write(out,&output.stdout)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_blueprints` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/build.rs:16
`crate::register_resources()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `activate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/src/preview.rs:81
`imp.chip.get()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `header_control` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/src/notification_stack/mod.rs:128
`holder.clone().downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `apply` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/src/event_list/mod.rs:127
`container.first_child().and_downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `heading_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/src/audio_popover/mod.rs:421
`heading_of(container).next_sibling().and_downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `slider_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/src/audio_popover/mod.rs:428
`slider.imp().start.first_child().and_downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `mute_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/src/audio_popover/mod.rs:437
`slider_of(container).next_sibling().and_downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `devices_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-widgets/src/audio_popover/mod.rs:444
`context.with_thread_default(work)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `run_in` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-panel/src/applet/testing.rs:10
`context.acquire()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `driven` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-panel/src/applet/testing.rs:14
`OwnedObjectPath::try_from(NO_FIX)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/geoclue.rs:37
`OwnedObjectPath::try_from(format!("/org/freedesktop/GeoClue2/Client/{ordinal}"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `spawn_client` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/geoclue.rs:78
`OwnedObjectPath::try_from(format!("/org/freedesktop/GeoClue2/Location/{ordinal}"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `push_fix` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/geoclue.rs:389
`std::fs::create_dir(&scratch)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:24
`std::fs::create_dir(&services)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:26
`std::fs::write(&config_path,config)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:43
`Command::new("dbus-daemon").arg("--config-file").arg(&config_path).args(["--nofork","--print-address=1"]).stdout(Stdio::piped()).stderr(Stdio::null()).spawn()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:51
`zbus::connection::Builder::address(self.address.as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `connection` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:61
`` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `connection` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:64
`child.stdout.as_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `printed_address` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:90
`std::io::BufReader::new(stdout).lines().next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `printed_address` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:94
`std::io::BufReader::new(stdout).lines().next().expect("an address")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `printed_address` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/mod.rs:95
`ObjectPath::try_from(path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `menu_path` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/tray.rs:126
`OwnedValue::try_from(value.clone())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `properties` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/tray.rs:401
`OwnedValue::try_from(Value::from((child.id,properties(child),children(child))))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `children` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-dbus/src/testing/tray.rs:414
`toml::to_string_pretty(&applet)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `applet_defaults` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-config/src/commented.rs:51
`serde_json::to_string_pretty(&schema)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `json_schema_document` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-config/src/lib.rs:41
`toml::to_string_pretty(&Config::default())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `document_body` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-config/src/lib.rs:112
`body.parse::<toml_edit::DocumentMut>()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `document_body` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-config/src/lib.rs:115
`tempfile::tempdir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `spawn` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-compositor-niri/src/niri/testing.rs:14
`UnixListener::bind(&socket)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `spawn` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-compositor-niri/src/niri/testing.rs:16
`tempfile::tempdir()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-compositor-hyprland/src/hyprland/testing.rs:70
`UnixListener::bind(dir.join(".socket.sock"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-compositor-hyprland/src/hyprland/testing.rs:74
`UnixListener::bind(dir.join(".socket2.sock"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-compositor-hyprland/src/hyprland/testing.rs:105
`std::process::Command::new("blueprint-compiler").args(["compile",src]).output()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `compile_blueprint` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-agents/build.rs:20
`std::fs::create_dir_all(dir)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_blueprint` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-agents/build.rs:28
`std::fs::write(out,&output.stdout)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_blueprint` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`). — crates/glimpse-agents/build.rs:30
What to do
Each row is a forced `Option`/`Result` no guard on its path proves present. Handle the absent case where it arises rather than forcing it: `?` to hand it to the caller, `if let` / `match` / `let … else` to branch on it, `unwrap_or` / `unwrap_or_default` / `unwrap_or_else` where a default is right. Where the value genuinely cannot be absent, say so in a way a reader can check from the line: test it first (`if x.is_none() { return … }`), look the key up with `contains_key` or the index against `len()`, or construct the value so it cannot be absent.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 10 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 — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (5 DOM element(s) < 25) — too little surface to assess accessibility.
AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — AX6 reached only 5% of this repository's production lines — rust (192,284 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev` in website/) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / The language 'kdl' is not loaded, falling back to 'txt' for syntax highlighting. / llmstxt » Dev server configured for serving plain text docs for LLMs / llmstxt » Build started, file collection cleared / vitepress v1.6.4 / ➜ Local: http://localhost:5173/glimpse/ / ➜ Network: use --host to expose" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — 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.
D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 1 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Python, Rust surface was not measured.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go, .py, .rs source were not judged.
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) — 6 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the node:test suite in sdk/sdk-ts/ ran but wrote no lcov report. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM1 Domain Modelling — applicable but not scored (3 signals for this style, 2 needed — the count is met but a required primary signal is absent): 2 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 38 value object(s); 24 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
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Go, JavaScript/TypeScript, Python, 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
S1 Web-Security Posture — No web surface: 622 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.
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — 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.
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — X26 reached only 3% of this repository's production lines — rust (192,284 lines), typescript (2,607 lines), javascript (166 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X3 Exception handling — X3 reached only 5% of this repository's production lines — rust (192,284 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
ED1 · Handler temporal coupling· Blocking call on the event loop · ×24
Blocking call on the event loop: watch.inode calls `std::fs::metadata` crates/glimpse-config/src/watch.rs:500— `watch.inode` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: clipboard.copy calls `block_on` crates/glimpse-lens/src/clipboard.rs:15— `clipboard.copy` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: probe.pam_stack calls `std::fs::read_to_string` crates/glimpse-lock/src/probe.rs:201— `probe.pam_stack` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: probe.shadow_mode calls `std::fs::metadata` crates/glimpse-lock/src/probe.rs:262— `probe.shadow_mode` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: probe.own_chkpwd calls `std::fs::metadata` crates/glimpse-lock/src/probe.rs:284— `probe.own_chkpwd` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: probe.read calls `std::fs::read_to_string` crates/glimpse-lock/src/probe.rs:298— `probe.read` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: user.current calls `std::fs::read_to_string` crates/glimpse-lock/src/user.rs:25— `user.current` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: spawn.unlink_if_ours calls `std::fs::metadata` crates/glimpse-services/src/services/exec/spawn.rs:92— `spawn.unlink_if_ours` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: spawn.unlink_if_ours calls `std::fs::remove_file` crates/glimpse-services/src/services/exec/spawn.rs:93— `spawn.unlink_if_ours` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::remove_file`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: SlotStream.start calls `std::fs::metadata` crates/glimpse-services/src/services/exec/spawn.rs:411— `SlotStream.start` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: CameraSource.rearm calls `std::fs::read_dir` crates/glimpse-services/src/services/privacy/source.rs:133— `CameraSource.rearm` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_dir`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: screens.connect calls `block_on` crates/glimpse-shot/src/adapters/screens.rs:69— `screens.connect` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `block_on`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: raster.store calls `std::fs::rename` crates/glimpse-widgets/src/raster.rs:402— `raster.store` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::rename`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: raster.store calls `std::fs::remove_file` crates/glimpse-widgets/src/raster.rs:404— `raster.store` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::remove_file`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: raster.evict calls `std::fs::read_dir` crates/glimpse-widgets/src/raster.rs:435— `raster.evict` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_dir`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: raster.evict calls `std::fs::metadata` crates/glimpse-widgets/src/raster.rs:439— `raster.evict` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::metadata`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: raster.evict calls `std::fs::remove_file` crates/glimpse-widgets/src/raster.rs:457— `raster.evict` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::remove_file`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: raster.evict calls `std::fs::remove_file` crates/glimpse-widgets/src/raster.rs:469— `raster.evict` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::remove_file`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: Scratch.new calls `std::fs::create_dir_all` crates/glimpsectl/src/commands/dev.rs:26— `Scratch.new` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::create_dir_all`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: OwnedPanel.start_with calls `std::fs::write` crates/glimpsectl/src/commands/dev.rs:125— `OwnedPanel.start_with` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::write`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: OwnedPanel.start_with calls `std::fs::write` crates/glimpsectl/src/commands/dev.rs:129— `OwnedPanel.start_with` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::write`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: run.locate calls `std::fs::read_dir` crates/glimpsectl/src/commands/run.rs:30— `run.locate` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_dir`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: run.settings calls `std::fs::read_to_string` crates/glimpsectl/src/commands/run.rs:59— `run.settings` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `std::fs::read_to_string`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Blocking call on the event loop: run.run_inner calls `recv` sdk/sdk-rs/src/run.rs:63— `run.run_inner` runs on the async event loop (it is async, an actor or framework handler, a hand-written `poll`, or called from one) and makes the blocking call `recv`: while it blocks, the loop's worker thread serves nothing else, so every task, message and request scheduled on it waits — and a blocking wait on a future that needs that worker can deadlock. Use the awaited twin (`tokio::time::sleep(..).await`, `tokio::fs`, an async channel/client), or move the work off the loop with `tokio::task::spawn_blocking`.
Dual write (no outbox): Keyboard.restore crates/glimpse-services/src/services/keyboard.rs:304— `Keyboard.restore` performs two independent DURABLE writes — a durable state write (`store.remove`, :315) and an independent publish to an event bus (`events.send`, :338) — in one command path with no shared transaction or outbox. A crash between the two leaves the stores diverged (one write committed, the other lost) or emits a phantom record. Wrap both in one transaction, or record the second write in the same store and dispatch it afterwards (a transactional outbox).
Low cohesion: ShotToolbar (LCOM4 19) crates/glimpse-widgets/src/shot_toolbar/imp.rs:10— ShotToolbar's methods fall into 19 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 19 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LockStage (LCOM4 13) crates/glimpse-widgets/src/lock_stage/imp.rs:22— LockStage's methods fall into 13 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 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Sparkline (LCOM4 12) crates/glimpse-widgets/src/sparkline.rs:145— Sparkline's methods fall into 12 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 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PowerPopover (LCOM4 11) crates/glimpse-widgets/src/power_popover/imp.rs:16— PowerPopover's methods fall into 11 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 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PasswordPrompt (LCOM4 10) crates/glimpse-widgets/src/password_prompt/imp.rs:7— PasswordPrompt's methods fall into 10 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 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ShotResultPage (LCOM4 10) crates/glimpse-widgets/src/shot_result_page/imp.rs:10— ShotResultPage's methods fall into 10 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 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Bars (LCOM4 8) crates/glimpse-widgets/src/bars.rs:120— Bars's methods fall into 8 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 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Row (LCOM4 8) crates/glimpse-widgets/src/row/imp.rs:35— Row's methods fall into 8 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 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AudioPopover (LCOM4 7) crates/glimpse-widgets/src/audio_popover/imp.rs:40— AudioPopover's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BluetoothPopover (LCOM4 7) crates/glimpse-widgets/src/bluetooth_popover/imp.rs:44— BluetoothPopover's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Calendar (LCOM4 7) crates/glimpse-widgets/src/calendar/imp.rs:28— Calendar's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CalendarPopover (LCOM4 7) crates/glimpse-widgets/src/calendar_popover/imp.rs:11— CalendarPopover's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ClipboardPopover (LCOM4 7) crates/glimpse-widgets/src/clipboard_popover/imp.rs:9— ClipboardPopover's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: EntryRow (LCOM4 7) crates/glimpse-widgets/src/entry_row/imp.rs:12— EntryRow's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NextEventPopover (LCOM4 7) crates/glimpse-widgets/src/next_event_popover/imp.rs:12— NextEventPopover's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ShotCapturePage (LCOM4 7) crates/glimpse-widgets/src/shot_capture_page/imp.rs:7— ShotCapturePage's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WeatherPopover (LCOM4 7) crates/glimpse-widgets/src/weather_popover/imp.rs:10— WeatherPopover's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Container (LCOM4 6) crates/glimpse-widgets/src/container/imp.rs:23— Container's methods fall into 6 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 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DisplayPopover (LCOM4 6) crates/glimpse-widgets/src/display_popover/imp.rs:31— DisplayPopover's methods fall into 6 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 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: IdlePopover (LCOM4 6) crates/glimpse-widgets/src/idle_popover/imp.rs:12— IdlePopover's methods fall into 6 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 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Lens (LCOM4 6) crates/glimpse-widgets/src/lens.rs:33— Lens's methods fall into 6 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 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NetworkPopover (LCOM4 6) crates/glimpse-widgets/src/network_popover/imp.rs:44— NetworkPopover's methods fall into 6 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 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PopoverShell (LCOM4 6) crates/glimpse-widgets/src/popover_shell/imp.rs:14— PopoverShell's methods fall into 6 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 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RangeBar (LCOM4 6) crates/glimpse-widgets/src/range_bar.rs:14— RangeBar's methods fall into 6 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 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Marks (LCOM4 5) crates/glimpse-lens/src/marks.rs:23— Marks's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
+ 21 more in this group — see findings.md.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×40
Recursive walk over a caller-supplied document has no depth cap sdk/sdk-ts/wire.ts:193— `oversized` is exported and takes `value: unknown` from its caller, and it calls itself at line 193 (`oversized`) with a piece of `value` (and at line 196) — and nowhere in `oversized` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `oversized` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap sdk/sdk-rs/src/protocol.rs:73— `oversized` is public and takes `value: &Value` from its caller, and it calls itself at line 73 with a piece of the document (and at line 75) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `oversized` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/workspaces_popover/mod.rs:33— `set_workspaces` is public and takes a `WorkspacesPopover` as its receiver from its caller, and it calls itself at line 33 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_workspaces` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/workspaces_popover/mod.rs:105— `connect_activated` is public and takes a `WorkspacesPopover` as its receiver from its caller, and it calls itself at line 105 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `connect_activated` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/workspace_list/mod.rs:63— `set_workspaces` is public and takes a `WorkspaceList` as its receiver from its caller, and it recurses at line 63 through `render` and back with a piece of the document (and at line 113) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_workspaces` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/workspace_list/mod.rs:89— `holders` is public and takes a `WorkspaceList` as its receiver from its caller, and it calls itself at line 89 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `holders` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/weather_popover/mod.rs:69— `set_unit` is public and takes a `WeatherPopover` as its receiver from its caller, and it calls itself at line 69 with a piece of the document (and at line 70) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_unit` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/weather_popover/mod.rs:75— `set_hours` is public and takes a `WeatherPopover` as its receiver from its caller, and it calls itself at line 75 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_hours` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/weather_popover/mod.rs:81— `set_days` is public and takes a `WeatherPopover` as its receiver from its caller, and it calls itself at line 81 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_days` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/tray_strip/mod.rs:67— `set_orientation` is public and takes a `TrayStrip` as its receiver from its caller, and it calls itself at line 67 with a piece of the document (and at line 76) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_orientation` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/toggle_row/imp.rs:154— `activate_from_user` is public, takes a document from its caller (line 107) and hands it to `apply_active`, which recurses at line 154 through `set_active` and back with a piece of the document (and at line 131) — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `apply_active` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/slider_row/imp.rs:61— `finish_drag` is public, takes a document from its caller (line 202) and hands it to `value`, which calls itself at line 61 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/slider_row/imp.rs:76— `constructed` is public, takes a document from its caller (line 243) and hands it to `set_value`, which calls itself at line 76 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_value` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/shot_result_page/mod.rs:108— `set_menu_model` is public and takes a `ShotResultPage` as its receiver from its caller, and it calls itself at line 108 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_menu_model` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/shot_result_page/mod.rs:143— `add_toast` is public and takes a `ShotResultPage` as its receiver from its caller, and it calls itself at line 143 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `add_toast` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/session_sheet/mod.rs:82— `has_actions` is public and takes a `SessionSheet` as its receiver from its caller, and it calls itself at line 82 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `has_actions` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/row/mod.rs:27— `set_start` is public and takes a `Row` as its receiver from its caller, and it calls itself at line 27 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_start` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/row/mod.rs:31— `clear_start` is public and takes a `Row` as its receiver from its caller, and it calls itself at line 31 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `clear_start` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/row/mod.rs:35— `set_end` is public and takes a `Row` as its receiver from its caller, and it calls itself at line 35 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_end` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/popover_shell/imp.rs:86— `constructed` is public, takes a document from its caller (line 113) and hands it to `set_size`, which calls itself at line 86 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_size` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/popover_shell/imp.rs:173— `measure` is public and takes a `PopoverShell` as its receiver from its caller, and it calls itself at line 173 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `measure` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/player_list/row.rs:103— `set_title` is public and takes a `PlayerRow` as its receiver from its caller, and it calls itself at line 103 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_title` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/player_list/row.rs:110— `set_subtitle` is public and takes a `PlayerRow` as its receiver from its caller, and it calls itself at line 110 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_subtitle` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/player_list/row.rs:117— `set_icon_name` is public and takes a `PlayerRow` as its receiver from its caller, and it calls itself at line 117 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `set_icon_name` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap crates/glimpse-widgets/src/password_prompt/imp.rs:132— `grab_focus` is public and takes a `PasswordPrompt` as its receiver from its caller, and it calls itself at line 132 with a piece of the document — and nowhere in the walk is a depth or nesting counter compared with a bound. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. When a Rust thread runs out of stack it is not unwound: the runtime reports the overflow and aborts the process, so `catch_unwind` does not stop it and every other request the process serves dies with it (spawned threads, a Tokio worker included, get 2 MiB by default). serde_json and serde_yaml stop parsing at 128 levels only on their default path; a value from `disable_recursion_limit`, from another format or parser, or built in code carries whatever nesting it was given. Thread a depth argument through `grab_focus` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
+ 15 more in this group — see findings.md.
X5 · Nullable reference types· Symbol treated as nullable, then dereferenced unguarded · ×39
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/build.rs:5— `std::fs::create_dir_all(parent)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_blueprints` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/build.rs:10— `std::process::Command::new("blueprint-compiler").args(["compile",src]).output()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `compile_blueprints` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/build.rs:16— `std::fs::write(out,&output.stdout)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.unwrap()` in `compile_blueprints` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/src/preview.rs:81— `crate::register_resources()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `activate` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/src/notification_stack/mod.rs:128— `imp.chip.get()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `header_control` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/src/event_list/mod.rs:127— `holder.clone().downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `apply` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/src/audio_popover/mod.rs:421— `container.first_child().and_downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `heading_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/src/audio_popover/mod.rs:428— `heading_of(container).next_sibling().and_downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `slider_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/src/audio_popover/mod.rs:437— `slider.imp().start.first_child().and_downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `mute_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-widgets/src/audio_popover/mod.rs:444— `slider_of(container).next_sibling().and_downcast()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `devices_of` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-panel/src/applet/testing.rs:10— `context.with_thread_default(work)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `run_in` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-panel/src/applet/testing.rs:14— `context.acquire()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `driven` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/geoclue.rs:37— `OwnedObjectPath::try_from(NO_FIX)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `new` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/geoclue.rs:78— `OwnedObjectPath::try_from(format!("/org/freedesktop/GeoClue2/Client/{ordinal}"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `spawn_client` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/geoclue.rs:389— `OwnedObjectPath::try_from(format!("/org/freedesktop/GeoClue2/Location/{ordinal}"))` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `push_fix` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:24— `std::fs::create_dir(&scratch)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:26— `std::fs::create_dir(&services)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:43— `std::fs::write(&config_path,config)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:51— `Command::new("dbus-daemon").arg("--config-file").arg(&config_path).args(["--nofork","--print-address=1"]).stdout(Stdio::piped()).stderr(Stdio::null()).spawn()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `start` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:61— `zbus::connection::Builder::address(self.address.as_str())` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `connection` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:64— `` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `connection` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:90— `child.stdout.as_mut()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `printed_address` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:94— `std::io::BufReader::new(stdout).lines().next()` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `printed_address` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/mod.rs:95— `std::io::BufReader::new(stdout).lines().next().expect("an address")` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `printed_address` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
Symbol treated as nullable, then dereferenced unguarded crates/glimpse-dbus/src/testing/tray.rs:126— `ObjectPath::try_from(path)` can be absent — it is an `Option` or `Result`, which is why it is forced — and `.expect()` in `menu_path` forces it with nothing on this path excluding `None`/`Err`: no `if let` or `match` arm that matched it present, no `let … else`, no `is_some()`/`is_ok()` test (or `is_none()`/`is_err()` test that leaves), no `assert!` of it, and for a lookup no proof the key or index exists. This line panics the first time the value is not there. Handle the absent case where it arises: propagate it with `?`, branch on it with `if let` / `match` / `let … else`, or give it a default (`unwrap_or`, `unwrap_or_default`, `unwrap_or_else`).
FileTooLong: src/elements.rs sdk/sdk-rs/src/elements.rs— FileTooLong — 1673 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 1173 over it, 3.35× 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: exec/tree.rs crates/glimpse-services/src/services/exec/tree.rs— FileTooLong — 1574 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 65 free functions. The bar is 500 significant lines; this is 1074 over it, 3.15× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: gui/overlay.rs crates/glimpse-shot/src/gui/overlay.rs— FileTooLong — 1351 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 73% of them inside a single declaration: Run (2 blocks, 100-1502). The bar is 500 significant lines; this is 851 over it, 2.70× 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: exec/mod.rs crates/glimpse-services/src/services/exec/mod.rs— FileTooLong — 1308 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 70% of them inside a single declaration: Exec (3 blocks, 472-1699). The bar is 500 significant lines; this is 808 over it, 2.62× 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: exec/dom.rs crates/glimpse-panel/src/applets/exec/dom.rs— FileTooLong — 1226 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: Dom (3 blocks, 62-1333). The bar is 500 significant lines; this is 726 over it, 2.45× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/app.rs crates/glimpse-lock/src/app.rs— FileTooLong — 1108 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 608 over it, 2.22× 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: network/mod.rs crates/glimpse-services/src/services/network/mod.rs— FileTooLong — 1100 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: Network (3 blocks, 400-1524). The bar is 500 significant lines; this is 600 over it, 2.20× 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: gui/canvas.rs crates/glimpse-shot/src/gui/canvas.rs— FileTooLong — 1063 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 563 over it, 2.13× 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: gui/result.rs crates/glimpse-shot/src/gui/result.rs— FileTooLong — 933 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 78% of them inside a single declaration: ResultFace (2 blocks, 65-1170). The bar is 500 significant lines; this is 433 over it, 1.87× 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/notifications.rs crates/glimpse-services/src/services/notifications.rs— FileTooLong — 879 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 379 over it, 1.76× 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: gui/app.rs crates/glimpse-shot/src/gui/app.rs— FileTooLong — 860 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 66% of them inside a single declaration: Shell (2 blocks, 202-959). The bar is 500 significant lines; this is 360 over it, 1.72× 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: brightness/mod.rs crates/glimpse-services/src/services/brightness/mod.rs— FileTooLong — 821 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 321 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: glimpse_sdk/elements.py sdk/sdk-py/glimpse_sdk/elements.py— FileTooLong — 818 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 318 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: src/app.rs crates/glimpse-notifications/src/app.rs— FileTooLong — 793 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 60% of them inside a single declaration: App (3 blocks, 148-794). The bar is 500 significant lines; this is 293 over it, 1.59× 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/calendar.rs crates/glimpse-services/src/services/calendar.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 35 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: audio/pulse.rs crates/glimpse-services/src/services/audio/pulse.rs— FileTooLong — 739 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 39 free functions. The bar is 500 significant lines; this is 239 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: bluetooth/mod.rs crates/glimpse-services/src/services/bluetooth/mod.rs— FileTooLong — 735 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 235 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: clients/weather.rs crates/glimpse-dbus/src/clients/weather.rs— FileTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 36 free functions. The bar is 500 significant lines; this is 137 over it, 1.27× 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: removable/mod.rs crates/glimpse-services/src/services/removable/mod.rs— FileTooLong — 625 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 125 over it, 1.25× 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/cli.rs crates/glimpsectl/src/cli.rs— FileTooLong — 625 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 125 over it, 1.25× 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: schema/applets.rs crates/glimpse-config/src/schema/applets.rs— FileTooLong — 624 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 124 over it, 1.25× 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: testing/tray.rs crates/glimpse-dbus/src/testing/tray.rs— FileTooLong — 611 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 111 over it, 1.22× 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: commands/package_manager.rs crates/glimpsectl/src/commands/package_manager.rs— FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 63% of them inside a single declaration: PackageManager (2 blocks, 68-717). The bar is 500 significant lines; this is 96 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: mpris/mod.rs crates/glimpse-services/src/services/mpris/mod.rs— FileTooLong — 581 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 81 over it, 1.16× 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/app.rs crates/glimpse-agents/src/app.rs— FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 74% of them inside a single declaration: App (3 blocks, 36-730). The bar is 500 significant lines; this is 65 over it, 1.13× 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.
Hotspot: crates/glimpse-services/src/services/exec/mod.rs crates/glimpse-services/src/services/exec/mod.rs:1036— crates/glimpse-services/src/services/exec/mod.rs changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 124 in Exec::handle at line 1036. 2 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/exec/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/glimpse-panel/src/applets/exec/dom.rs crates/glimpse-panel/src/applets/exec/dom.rs:874— crates/glimpse-panel/src/applets/exec/dom.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 111 in Dom::dress at line 874. 1 of those changes was a fix/bug commit, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-panel/src/applets/exec/dom.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/glimpse-panel/src/app.rs crates/glimpse-panel/src/app.rs:181— crates/glimpse-panel/src/app.rs changed 68 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in App::update at line 181. 3 of those changes were fix/bug commits, and the other 65 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-panel/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/glimpse-lock/src/app.rs crates/glimpse-lock/src/app.rs:299— crates/glimpse-lock/src/app.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in App::update at line 299. 1 of those changes was a fix/bug commit, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-lock/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/glimpsectl/src/commands/run.rs crates/glimpsectl/src/commands/run.rs:179— crates/glimpsectl/src/commands/run.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in glimpsectl::commands::run::applets_run at line 179. 1 of those changes was a fix/bug commit, and the other 11 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpsectl/src/commands/run.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/glimpse-notifications/src/app.rs crates/glimpse-notifications/src/app.rs:242— crates/glimpse-notifications/src/app.rs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in App::update at line 242. 1 of those changes was a fix/bug commit, 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-notifications/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/glimpse-panel/src/applet/runtime.rs crates/glimpse-panel/src/applet/runtime.rs:324— crates/glimpse-panel/src/applet/runtime.rs changed 38 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in AppletRuntime::update at line 324. 1 of those changes was a fix/bug commit, 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-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-panel/src/applet/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/glimpse-services/src/services/notifications.rs crates/glimpse-services/src/services/notifications.rs:328— crates/glimpse-services/src/services/notifications.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Notifications::dispatch at line 328. 2 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/notifications.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/glimpse-services/src/services/network/mod.rs crates/glimpse-services/src/services/network/mod.rs:918— crates/glimpse-services/src/services/network/mod.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in Network::merge at line 918. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/network/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/glimpse-dbus/src/clients/idle.rs crates/glimpse-dbus/src/clients/idle.rs:412— crates/glimpse-dbus/src/clients/idle.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in glimpse_dbus::clients::idle::follow_provider at line 412. 1 of those changes was a fix/bug commit, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-dbus/src/clients/idle.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/glimpse-services/src/services/weather/mod.rs crates/glimpse-services/src/services/weather/mod.rs:340— crates/glimpse-services/src/services/weather/mod.rs changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in Weather::handle at line 340. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/weather/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/glimpse-services/src/services/bluetooth/mod.rs crates/glimpse-services/src/services/bluetooth/mod.rs:451— crates/glimpse-services/src/services/bluetooth/mod.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Bluetooth::handle at line 451. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/bluetooth/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/glimpse-panel/src/applets/exec/mod.rs crates/glimpse-panel/src/applets/exec/mod.rs:139— crates/glimpse-panel/src/applets/exec/mod.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in Exec::refresh at line 139. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-panel/src/applets/exec/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/glimpse-services/src/services/exec/spawn.rs crates/glimpse-services/src/services/exec/spawn.rs:253— crates/glimpse-services/src/services/exec/spawn.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in SlotStream::read at line 253. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/exec/spawn.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/glimpse-shot/src/gui/overlay.rs crates/glimpse-shot/src/gui/overlay.rs:216— crates/glimpse-shot/src/gui/overlay.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Run::perform at line 216. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-shot/src/gui/overlay.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/glimpse-services/src/services/tray/mod.rs crates/glimpse-services/src/services/tray/mod.rs:265— crates/glimpse-services/src/services/tray/mod.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in Tray::handle at line 265. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/tray/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/glimpse-agents/src/app.rs crates/glimpse-agents/src/app.rs:286— crates/glimpse-agents/src/app.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in App::ingest at line 286. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-agents/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/glimpse-shot/src/cli.rs crates/glimpse-shot/src/cli.rs:497— crates/glimpse-shot/src/cli.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in glimpse_shot::cli::validate_annotate at line 497. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-shot/src/cli.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/glimpse-services/src/services/audio/mod.rs crates/glimpse-services/src/services/audio/mod.rs:239— crates/glimpse-services/src/services/audio/mod.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Audio::run at line 239. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/audio/mod.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/glimpse-dbus/src/clients/follower.rs crates/glimpse-dbus/src/clients/follower.rs:175— crates/glimpse-dbus/src/clients/follower.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in glimpse_dbus::clients::follower::follow_snapshots at line 175. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-dbus/src/clients/follower.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/glimpse-lens/src/session.rs crates/glimpse-lens/src/session.rs:316— crates/glimpse-lens/src/session.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in glimpse_lens::session::connect at line 316. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-lens/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.
Hotspot: crates/glimpse-dbus/src/clients/settings.rs crates/glimpse-dbus/src/clients/settings.rs:218— crates/glimpse-dbus/src/clients/settings.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in glimpse_dbus::clients::settings::follow at line 218. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-dbus/src/clients/settings.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: sdk/sdk-go/sdk/run.go sdk/sdk-go/sdk/run.go:32— sdk/sdk-go/sdk/run.go changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in sdk.run at line 32. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- sdk/sdk-go/sdk/run.go`: 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/glimpse-services/src/services/desktop_mode.rs crates/glimpse-services/src/services/desktop_mode.rs:147— crates/glimpse-services/src/services/desktop_mode.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in DesktopMode::handle at line 147. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-services/src/services/desktop_mode.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/glimpse-lock/src/logind.rs crates/glimpse-lock/src/logind.rs:193— crates/glimpse-lock/src/logind.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Logind::follow at line 193. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 22:41:07 +01:00' --until='2026-11-16 22:41:07 +01:00' --full-history --no-merges -- crates/glimpse-lock/src/logind.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.
Duplicated block (9 lines × 2) crates/glimpse-notifications/src/app.rs:944— crates/glimpse-notifications/src/app.rs:944-952 | crates/glimpse-panel/src/applets/notifications/indicator.rs:353-361 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-notifications/src/app.rs:944` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/glimpse-panel/src/app.rs:641— crates/glimpse-panel/src/app.rs:641-649 | crates/glimpse-wallpaper/src/app.rs:310-318 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/glimpse-panel/src/applets/display/indicator.rs:125— crates/glimpse-panel/src/applets/display/indicator.rs:125-133 | crates/glimpse-panel/src/applets/display/indicator.rs:182-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/display/indicator.rs:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/glimpse-panel/src/applets/exec/dom.rs:605— crates/glimpse-panel/src/applets/exec/dom.rs:605-613 | crates/glimpse-panel/src/applets/exec/dom.rs:634-642 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/exec/dom.rs:605` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/glimpse-services/src/services/brightness/mod.rs:376— crates/glimpse-services/src/services/brightness/mod.rs:376-384 | crates/glimpse-services/src/services/brightness/mod.rs:432-440 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/brightness/mod.rs:376` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:200— crates/glimpse-shot/src/gui/overlay.rs:200-208 | crates/glimpse-shot/src/gui/result.rs:1004-1012 — before extracting anything, compare `crates/glimpse-shot/src/gui/overlay.rs` and `crates/glimpse-shot/src/gui/result.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/overlay.rs:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/glimpse-shot/src/gui/overlay.rs:196` calls `effects` and `crates/glimpse-shot/src/gui/result.rs:1003` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) crates/glimpse-shot/src/portal.rs:468— crates/glimpse-shot/src/portal.rs:468-476 | crates/glimpse-wallpaper/src/portal.rs:228-236 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/portal.rs:468` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/glimpse-widgets/src/bars.rs:294— crates/glimpse-widgets/src/bars.rs:294-302 | crates/glimpse-widgets/src/sparkline.rs:405-413 — before extracting anything, compare `crates/glimpse-widgets/src/bars.rs` and `crates/glimpse-widgets/src/sparkline.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) crates/glimpse-widgets/src/choice_list/imp.rs:29— crates/glimpse-widgets/src/choice_list/imp.rs:29-37 | crates/glimpse-widgets/src/keyboard_popover/imp.rs:47-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/glimpse-widgets/src/entry_row/imp.rs:101— crates/glimpse-widgets/src/entry_row/imp.rs:101-109 | crates/glimpse-widgets/src/slider_row/imp.rs:193-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/glimpse-widgets/src/track_card/imp.rs:51— crates/glimpse-widgets/src/track_card/imp.rs:51-59 | crates/glimpse-widgets/src/transport/imp.rs:164-172 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/glimpsectl/src/commands/panel.rs:543— crates/glimpsectl/src/commands/panel.rs:543-551 | crates/glimpsectl/src/commands/status.rs:80-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpsectl/src/commands/panel.rs:543` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/glimpse-widgets/src/calendar/imp.rs:247— crates/glimpse-widgets/src/calendar/imp.rs:247-255 | crates/glimpse-widgets/src/calendar_popover/imp.rs:47-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/calendar/imp.rs:247` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-widgets/src/calendar_popover/imp.rs:56` calls `builder`, `param_types`, `static_type` and `crates/glimpse-widgets/src/calendar/imp.rs:256` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) crates/glimpse-panel/src/applets/power/mod.rs:106— crates/glimpse-panel/src/applets/power/mod.rs:106-114 | crates/glimpse-panel/src/applets/weather/mod.rs:204-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/glimpse-lens/src/lens.rs:49— crates/glimpse-lens/src/lens.rs:49-57 | crates/glimpse-lens/src/session.rs:139-147 — before extracting anything, compare `crates/glimpse-lens/src/lens.rs` and `crates/glimpse-lens/src/session.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-lens/src/session.rs:148` calls `default` and `crates/glimpse-lens/src/lens.rs:58` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:73— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:73-81 | crates/glimpse-widgets/src/network_popover/mod.rs:124-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) crates/glimpse-calendar/src/services.rs:56— crates/glimpse-calendar/src/services.rs:56-64 | crates/glimpse-weather/src/services.rs:55-63 — 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/glimpse-shot/src/portal.rs:392— crates/glimpse-shot/src/portal.rs:392-400 | crates/glimpse-wallpaper/src/portal.rs:125-133 — 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/glimpse-shot/src/portal.rs:402— crates/glimpse-shot/src/portal.rs:402-410 | crates/glimpse-wallpaper/src/portal.rs:135-143 — 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/glimpse-panel/src/applets/places/indicator.rs:42— crates/glimpse-panel/src/applets/places/indicator.rs:42-50 | crates/glimpse-panel/src/applets/removable/indicator.rs:42-50 — 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/glimpse-widgets/src/notification_stack/mod.rs:467— crates/glimpse-widgets/src/notification_stack/mod.rs:467-475 | crates/glimpse-widgets/src/notifications_popover/mod.rs:249-257 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/notification_stack/mod.rs:467` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/glimpsectl/src/commands/applets_author.rs:124— crates/glimpsectl/src/commands/applets_author.rs:124-132 | crates/glimpsectl/src/commands/package_manager.rs:104-112 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpsectl/src/commands/applets_author.rs:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/glimpse-panel/src/applets/clipboard/indicator.rs:605— crates/glimpse-panel/src/applets/clipboard/indicator.rs:605-613 | crates/glimpse-panel/src/applets/clipboard/indicator.rs:636-644 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/clipboard/indicator.rs:605` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/glimpse-widgets/src/bluetooth_popover/imp.rs:135— crates/glimpse-widgets/src/bluetooth_popover/imp.rs:135-143 | crates/glimpse-widgets/src/idle_popover/imp.rs:79-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/bluetooth_popover/imp.rs:135` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
MethodTooLong: Exec.handle crates/glimpse-services/src/services/exec/mod.rs:1036— MethodTooLong — handle runs 517 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 417 over it, 5.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Dom.dress crates/glimpse-panel/src/applets/exec/dom.rs:874— MethodTooLong — dress runs 334 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 234 over it, 3.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Dom.build crates/glimpse-panel/src/applets/exec/dom.rs:486— MethodTooLong — build runs 316 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 216 over it, 3.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Run.wire crates/glimpse-shot/src/gui/overlay.rs:556— MethodTooLong — wire runs 266 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 166 over it, 2.66× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: App.update crates/glimpse-lock/src/app.rs:299— MethodTooLong — update runs 173 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 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Network.popover crates/glimpse-panel/src/applets/network/indicator.rs:248— MethodTooLong — popover runs 169 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 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Network.run crates/glimpse-services/src/services/network/mod.rs:1298— MethodTooLong — run runs 157 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 57 over it, 1.57× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Display.popover crates/glimpse-panel/src/applets/display/indicator.rs:94— MethodTooLong — popover runs 152 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 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Audio.popover crates/glimpse-panel/src/applets/audio/indicator.rs:78— MethodTooLong — popover runs 151 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 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Clipboard.popover crates/glimpse-panel/src/applets/clipboard/indicator.rs:545— MethodTooLong — popover runs 146 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 46 over it, 1.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PanelServices.start_with_buses crates/glimpse-panel/src/services.rs:90— MethodTooLong — start_with_buses runs 137 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 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Bluetooth.popover crates/glimpse-panel/src/applets/bluetooth/indicator.rs:66— MethodTooLong — popover runs 134 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 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Run.open crates/glimpse-shot/src/gui/overlay.rs:401— MethodTooLong — open runs 127 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 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Audio.run crates/glimpse-services/src/services/audio/mod.rs:239— MethodTooLong — run runs 119 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 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Network.build crates/glimpse-services/src/services/network/mod.rs:1052— MethodTooLong — build runs 119 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 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: App.ingest crates/glimpse-agents/src/app.rs:286— MethodTooLong — ingest runs 116 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 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Network.handle crates/glimpse-services/src/services/network/mod.rs:631— MethodTooLong — handle runs 116 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 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ResultFace.wire_pointer crates/glimpse-shot/src/gui/result.rs:339— MethodTooLong — wire_pointer 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.
MethodTooLong: ResultFace.wire_keys crates/glimpse-shot/src/gui/result.rs:523— MethodTooLong — wire_keys runs 105 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 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: OwnedPanel.start_with crates/glimpsectl/src/commands/dev.rs:61— MethodTooLong — start_with runs 105 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 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (7 lines × 2) crates/glimpse-compositor-hyprland/src/hyprland/outputs.rs:213— crates/glimpse-compositor-hyprland/src/hyprland/outputs.rs:213-219 | crates/glimpse-wayland/src/wire.rs:137-143 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-compositor-hyprland/src/hyprland/outputs.rs:213` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/glimpse-idle/src/main.rs:34— crates/glimpse-idle/src/main.rs:34-40 | crates/glimpse-sunset/src/main.rs:33-39 — before extracting anything, compare `crates/glimpse-idle/src/main.rs` and `crates/glimpse-sunset/src/main.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-idle/src/main.rs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/glimpse-lens/src/lens.rs:122— crates/glimpse-lens/src/lens.rs:122-128 | crates/glimpse-lens/src/session.rs:209-215 — before extracting anything, compare `crates/glimpse-lens/src/lens.rs` and `crates/glimpse-lens/src/session.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-lens/src/session.rs:216` calls `add_overlay` and `crates/glimpse-lens/src/lens.rs:129` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) crates/glimpse-services/src/services/battery.rs:335— crates/glimpse-services/src/services/battery.rs:335-341 | crates/glimpse-services/src/services/battery.rs:358-364 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/battery.rs:335` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/glimpse-services/src/services/tray/watcher.rs:47— crates/glimpse-services/src/services/tray/watcher.rs:47-53 | crates/glimpse-services/src/services/tray/watcher.rs:161-167 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/tray/watcher.rs:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:715— crates/glimpse-shot/src/gui/overlay.rs:715-721 | crates/glimpse-shot/src/gui/overlay.rs:738-744 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/overlay.rs:715` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/glimpse-shot/src/gui/overlay.rs:737` calls `is_some` and `crates/glimpse-shot/src/gui/overlay.rs:713` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:254— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:254-260 | crates/glimpse-widgets/src/network_popover/mod.rs:348-354 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/bluetooth_popover/mod.rs:254` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-widgets/src/bluetooth_popover/mod.rs:261` calls `imp`, `borrow`, `set_details` and `crates/glimpse-widgets/src/network_popover/mod.rs:355` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) crates/glimpse-panel/src/app.rs:479— crates/glimpse-panel/src/app.rs:479-485 | crates/glimpse-wallpaper/src/app.rs:196-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 (7 lines × 2) crates/glimpse-shot/src/notify.rs:419— crates/glimpse-shot/src/notify.rs:419-425 | crates/glimpse-wallpaper/src/portal/notify.rs:43-49 — before extracting anything, compare `crates/glimpse-shot/src/notify.rs` and `crates/glimpse-wallpaper/src/portal/notify.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-shot/src/notify.rs:427` calls `file_uri`, `for_path`, `uri` and `crates/glimpse-wallpaper/src/portal/notify.rs:51` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) crates/glimpse-shot/src/portal.rs:574— crates/glimpse-shot/src/portal.rs:574-580 | crates/glimpse-wallpaper/src/portal/request.rs:57-63 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/portal.rs:574` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/glimpse-widgets/src/audio_popover/mod.rs:192— crates/glimpse-widgets/src/audio_popover/mod.rs:192-198 | crates/glimpse-widgets/src/bluetooth_popover/mod.rs:97-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/glimpse-widgets/src/network_popover/mod.rs:231— crates/glimpse-widgets/src/network_popover/mod.rs:231-237 | crates/glimpse-widgets/src/places_popover/mod.rs:67-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/glimpse-services/src/services/bluetooth/mod.rs:158— crates/glimpse-services/src/services/bluetooth/mod.rs:158-164 | crates/glimpse-services/src/services/network/mod.rs:243-249 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/glimpse-widgets/src/bluetooth_popover/imp.rs:88— crates/glimpse-widgets/src/bluetooth_popover/imp.rs:88-94 | crates/glimpse-widgets/src/removable_popover/imp.rs:67-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/glimpse-widgets/src/workspace_list/mod.rs:74— crates/glimpse-widgets/src/workspace_list/mod.rs:74-80 | crates/glimpse-widgets/src/workspace_section/mod.rs:53-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/glimpse-widgets/src/action_row/imp.rs:27— crates/glimpse-widgets/src/action_row/imp.rs:27-33 | crates/glimpse-widgets/src/toggle_row/imp.rs:51-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/action_row/imp.rs:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/glimpse-agents/src/bluetooth/mod.rs:240— crates/glimpse-agents/src/bluetooth/mod.rs:240-246 | crates/glimpse-agents/src/obex/mod.rs:470-476 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-agents/src/bluetooth/mod.rs:240` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) scripts/docs-screenshots.py:846— scripts/docs-screenshots.py:846-852 | scripts/release-video.py:354-360 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) crates/glimpse-lock/src/main.rs:95— crates/glimpse-lock/src/main.rs:95-100 | crates/glimpse-panel/src/main.rs:55-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-lock/src/main.rs:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/glimpse-widgets/src/display_popover/imp.rs:100— crates/glimpse-widgets/src/display_popover/imp.rs:100-105 | crates/glimpse-widgets/src/source_list/imp.rs:29-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/display_popover/imp.rs:100` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/glimpse-widgets/src/idle_popover/imp.rs:61— crates/glimpse-widgets/src/idle_popover/imp.rs:61-66 | crates/glimpse-widgets/src/power_popover/imp.rs:102-107 — 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/glimpse-widgets/src/notifications_popover/mod.rs:163— crates/glimpse-widgets/src/notifications_popover/mod.rs:163-168 | crates/glimpse-widgets/src/notifications_popover/mod.rs:178-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/notifications_popover/mod.rs:163` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/glimpsectl/src/commands/panel.rs:273— crates/glimpsectl/src/commands/panel.rs:273-278 | crates/glimpsectl/src/commands/watch.rs:57-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpsectl/src/commands/panel.rs:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/glimpse-widgets/src/raster.rs:163— crates/glimpse-widgets/src/raster.rs:163-168 | crates/glimpse-widgets/src/raster.rs:181-186 — 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/glimpse-lens/src/lens.rs:88— crates/glimpse-lens/src/lens.rs:88-93 | crates/glimpse-lens/src/session.rs:178-183 — before extracting anything, compare `crates/glimpse-lens/src/lens.rs` and `crates/glimpse-lens/src/session.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) crates/glimpse-shot/src/notify.rs:431— crates/glimpse-shot/src/notify.rs:431-436 | crates/glimpse-wallpaper/src/portal/notify.rs:51-56 — before extracting anything, compare `crates/glimpse-shot/src/notify.rs` and `crates/glimpse-wallpaper/src/portal/notify.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) crates/glimpse-widgets/src/applet_popover/imp.rs:58— crates/glimpse-widgets/src/applet_popover/imp.rs:58-63 | crates/glimpse-widgets/src/container/imp.rs:169-174 — 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/glimpse-widgets/src/applet_popover/imp.rs:69— crates/glimpse-widgets/src/applet_popover/imp.rs:69-74 | crates/glimpse-widgets/src/container/imp.rs:180-185 — 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/glimpse-widgets/src/mpris_popover/imp.rs:118— crates/glimpse-widgets/src/mpris_popover/imp.rs:118-123 | crates/glimpse-widgets/src/popover_shell/imp.rs:198-203 — 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/glimpse-widgets/src/power_popover/imp.rs:175— crates/glimpse-widgets/src/power_popover/imp.rs:175-180 | crates/glimpse-widgets/src/row/imp.rs:336-341 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `widget` to `&impl gtk4::prelude::IsA<gtk4::Widget>` in one and `&impl IsA<gtk4::Widget>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) crates/glimpse-calendar/src/provider.rs:61— crates/glimpse-calendar/src/provider.rs:61-66 | crates/glimpse-notifications/src/provider.rs:129-134 — 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/glimpse-services/src/services/bluetooth/source.rs:35— crates/glimpse-services/src/services/bluetooth/source.rs:35-40 | crates/glimpse-services/src/services/network/source.rs:35-40 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) crates/glimpsectl/src/commands/idle.rs:14— crates/glimpsectl/src/commands/idle.rs:14-19 | crates/glimpsectl/src/commands/settings.rs:85-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) crates/glimpse-widgets/src/indicator_group/imp.rs:34— crates/glimpse-widgets/src/indicator_group/imp.rs:34-39 | crates/glimpse-widgets/src/power_popover/imp.rs:93-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/indicator_group/imp.rs:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/glimpse-widgets/src/event_list/imp.rs:63— crates/glimpse-widgets/src/event_list/imp.rs:63-68 | crates/glimpse-widgets/src/world_clock/imp.rs:29-34 — 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/glimpse-widgets/src/clipboard_list/mod.rs:307— crates/glimpse-widgets/src/clipboard_list/mod.rs:307-312 | crates/glimpse-widgets/src/inhibitor_list/mod.rs:104-109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/glimpse-dbus/src/clients/idle.rs:533— crates/glimpse-dbus/src/clients/idle.rs:533-540 | crates/glimpse-dbus/src/clients/idle.rs:564-571 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-dbus/src/clients/idle.rs:533` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/glimpse-panel/src/applets/audio/indicator.rs:315— crates/glimpse-panel/src/applets/audio/indicator.rs:315-322 | crates/glimpse-panel/src/applets/bluetooth/indicator.rs:298-305 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/audio/indicator.rs:315` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) crates/glimpse-services/src/services/battery.rs:631— crates/glimpse-services/src/services/battery.rs:631-638 | crates/glimpse-services/src/services/battery.rs:645-652 — 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/glimpse-services/src/services/bluetooth/failure.rs:35— crates/glimpse-services/src/services/bluetooth/failure.rs:35-42 | crates/glimpse-services/src/services/network/failure.rs:57-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/failure.rs:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/glimpse-services/src/services/bluetooth/mod.rs:452— crates/glimpse-services/src/services/bluetooth/mod.rs:452-459 | crates/glimpse-services/src/services/network/mod.rs:632-639 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/mod.rs:452` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/glimpse-services/src/services/privacy/screencast.rs:168— crates/glimpse-services/src/services/privacy/screencast.rs:168-175 | crates/glimpse-services/src/services/privacy/screencast.rs:185-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/privacy/screencast.rs:168` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) crates/glimpse-shot/src/notify.rs:251— crates/glimpse-shot/src/notify.rs:251-258 | crates/glimpse-wallpaper/src/portal/notify.rs:150-157 — before extracting anything, compare `crates/glimpse-shot/src/notify.rs` and `crates/glimpse-wallpaper/src/portal/notify.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/notify.rs:251` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/glimpse-widgets/src/bars.rs:284— crates/glimpse-widgets/src/bars.rs:284-291 | crates/glimpse-widgets/src/sparkline.rs:465-472 — before extracting anything, compare `crates/glimpse-widgets/src/bars.rs` and `crates/glimpse-widgets/src/sparkline.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) crates/glimpse-widgets/src/choice_list/mod.rs:66— crates/glimpse-widgets/src/choice_list/mod.rs:66-73 | crates/glimpse-widgets/src/player_list/mod.rs:70-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/choice_list/mod.rs:66` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/glimpse-services/src/services/exec/launcher.rs:62— crates/glimpse-services/src/services/exec/launcher.rs:62-69 | crates/glimpsectl/src/commands/applets.rs:186-193 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/glimpse-widgets/src/bars.rs:253— crates/glimpse-widgets/src/bars.rs:253-260 | crates/glimpse-widgets/src/sparkline.rs:355-362 — before extracting anything, compare `crates/glimpse-widgets/src/bars.rs` and `crates/glimpse-widgets/src/sparkline.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) crates/glimpse-services/src/services/exec/tree.rs:1805— crates/glimpse-services/src/services/exec/tree.rs:1805-1812 | sdk/sdk-rs/src/protocol.rs:71-78 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) crates/glimpse-shot/src/gui/canvas.rs:1279— crates/glimpse-shot/src/gui/canvas.rs:1279-1286 | crates/glimpse-shot/src/render.rs:292-299 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:48— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:48-55 | crates/glimpse-widgets/src/network_popover/mod.rs:47-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/glimpse-panel/src/applets/keyboard/indicator.rs:25— crates/glimpse-panel/src/applets/keyboard/indicator.rs:25-32 | crates/glimpse-panel/src/applets/session/mod.rs:66-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) crates/glimpse-services/src/services/exec/mod.rs:1274— crates/glimpse-services/src/services/exec/mod.rs:1274-1281 | crates/glimpse-services/src/services/exec/mod.rs:1291-1298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/exec/mod.rs:1274` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/glimpse-widgets/src/event_list/imp.rs:53— crates/glimpse-widgets/src/event_list/imp.rs:53-60 | crates/glimpse-widgets/src/session_popover/imp.rs:51-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/event_list/imp.rs:53` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
IC1 · Incompleteness & stubs· Empty method body · ×17
Empty method body — does nothing with its inputs crates/glimpse-agents/src/bluetooth/mod.rs:306— `withdraw_device` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-agents/src/queue.rs:58— `refuse` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-config/src/load.rs:82— `init` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-idle/src/idle.rs:98— `send` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-idle/src/inhibitors/portal.rs:173— `query_end_response` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-idle/src/inhibitors/portal.rs:199— `close` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-lock/src/logind.rs:397— `ended` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-panel/src/applet/mod.rs:254— `typing` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-panel/src/applet/runtime.rs:697— `configure` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-panel/src/applet/runtime.rs:704— `set_orientation` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-panel/src/applet/runtime.rs:711— `set_slot` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-panel/src/applet/runtime.rs:715— `set_placement` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-services/src/services/notifications.rs:947— `close_notification` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-services/src/services/tray/watcher.rs:34— `announce` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-shot/src/portal.rs:547— `unexport` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-wayland/src/selection/protocol.rs:103— `event` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
Empty method body — does nothing with its inputs crates/glimpse-widgets/src/raster.rs:357— `touch` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×16
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/hero/imp.rs:48— crates/glimpse-widgets/src/hero/imp.rs:48-54 | crates/glimpse-widgets/src/notification_header/imp.rs:52-58 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-services/src/services/places/sources.rs:17— crates/glimpse-services/src/services/places/sources.rs:17-23 | crates/glimpse-wallpaper/src/portal.rs:71-77 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/range_bar.rs:97— crates/glimpse-widgets/src/range_bar.rs:97-103 | crates/glimpse-widgets/src/shot_region/imp.rs:227-233 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/audio_popover/mod.rs:461— crates/glimpse-widgets/src/audio_popover/mod.rs:461-467 | crates/glimpse-widgets/src/places_popover/mod.rs:195-201 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-services/src/services/printing/call.rs:69— crates/glimpse-services/src/services/printing/call.rs:69-75 | crates/glimpse-utils/src/process.rs:100-107 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-idle/src/services.rs:153— crates/glimpse-idle/src/services.rs:153-159 | crates/glimpse-sunset/src/services.rs:80-86 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-panel/src/applets/network/indicator.rs:234— crates/glimpse-panel/src/applets/network/indicator.rs:234-242 | crates/glimpse-panel/src/applets/printing/indicator.rs:44-50 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-panel/src/applets/pager/mod.rs:84— crates/glimpse-panel/src/applets/pager/mod.rs:84-90 | crates/glimpse-panel/src/applets/tray/mod.rs:157-163 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-services/src/services/bluetooth/mod.rs:793— crates/glimpse-services/src/services/bluetooth/mod.rs:793-800 | crates/glimpse-services/src/services/removable/mod.rs:580-586 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:83— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:83-89 | crates/glimpse-widgets/src/network_popover/mod.rs:145-153 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-shot/src/doc/document.rs:29— crates/glimpse-shot/src/doc/document.rs:29-35 | crates/glimpse-shot/src/render.rs:222-228 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/idle_popover/imp.rs:43— crates/glimpse-widgets/src/idle_popover/imp.rs:43-49 | crates/glimpse-widgets/src/network_popover/imp.rs:108-114 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/printing_popover/mod.rs:57— crates/glimpse-widgets/src/printing_popover/mod.rs:57-63 | crates/glimpse-widgets/src/privacy_popover/mod.rs:51-57 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/choice_list/mod.rs:55— crates/glimpse-widgets/src/choice_list/mod.rs:55-61 | crates/glimpse-widgets/src/player_list/mod.rs:51-57 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/shot_result_page/mod.rs:126— crates/glimpse-widgets/src/shot_result_page/mod.rs:126-132 | crates/glimpse-widgets/src/shot_toolbar/mod.rs:126-132 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) crates/glimpse-widgets/src/shot_toolbar/mod.rs:134— crates/glimpse-widgets/src/shot_toolbar/mod.rs:134-140 | crates/glimpse-widgets/src/status_island/mod.rs:59-65 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×13
Edited copy of a member (14 corresponding lines) crates/glimpse-services/src/services/exec/launcher.rs:61— crates/glimpse-services/src/services/exec/launcher.rs:61-74 | crates/glimpsectl/src/commands/applets.rs:185-198 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-calendar/src/services.rs:17— crates/glimpse-calendar/src/services.rs:17-34 | crates/glimpse-weather/src/services.rs:17-30 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-widgets/src/entry_row/imp.rs:149— crates/glimpse-widgets/src/entry_row/imp.rs:149-168 | crates/glimpse-widgets/src/player_list/row.rs:62-75 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-panel/src/applets/pager/mod.rs:235— crates/glimpse-panel/src/applets/pager/mod.rs:235-248 | crates/glimpse-panel/src/applets/pager/mod.rs:250-267 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-widgets/src/notifications_popover/mod.rs:288— crates/glimpse-widgets/src/notifications_popover/mod.rs:288-301 | crates/glimpse-widgets/src/notifications_popover/mod.rs:306-319 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-widgets/src/container/imp.rs:76— crates/glimpse-widgets/src/container/imp.rs:76-89 | crates/glimpse-widgets/src/container/imp.rs:91-104 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-dbus/src/testing/geoclue.rs:200— crates/glimpse-dbus/src/testing/geoclue.rs:200-215 | crates/glimpse-dbus/src/testing/geoclue.rs:217-230 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) sdk/sdk-rs/src/widget.rs:123— sdk/sdk-rs/src/widget.rs:123-136 | sdk/sdk-rs/src/widget.rs:182-195 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-widgets/src/player_list/mod.rs:93— crates/glimpse-widgets/src/player_list/mod.rs:93-106 | crates/glimpse-widgets/src/workspace_list/mod.rs:123-136 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-services/src/services/bluetooth/source.rs:216— crates/glimpse-services/src/services/bluetooth/source.rs:216-229 | crates/glimpse-services/src/services/network/source.rs:268-281 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-widgets/src/display_popover/imp.rs:77— crates/glimpse-widgets/src/display_popover/imp.rs:77-91 | crates/glimpse-widgets/src/power_popover/imp.rs:71-84 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-widgets/src/shot_toolbar/mod.rs:24— crates/glimpse-widgets/src/shot_toolbar/mod.rs:24-37 | crates/glimpse-widgets/src/shot_toolbar/mod.rs:39-55 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/glimpse-notifications/src/app.rs:568— crates/glimpse-notifications/src/app.rs:568-582 | crates/glimpse-notifications/src/app.rs:584-597 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10 lines × 2) crates/glimpse-services/src/services/audio/pulse.rs:873— crates/glimpse-services/src/services/audio/pulse.rs:873-882 | crates/glimpse-services/src/services/audio/pulse.rs:930-939 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/audio/pulse.rs:873` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/glimpse-services/src/services/bluetooth/mod.rs:465— crates/glimpse-services/src/services/bluetooth/mod.rs:465-474 | crates/glimpse-services/src/services/network/mod.rs:668-677 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/mod.rs:465` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-services/src/services/network/mod.rs:678` calls `forget_everything` and `crates/glimpse-services/src/services/bluetooth/mod.rs:475` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) crates/glimpse-services/src/services/bluetooth/source.rs:84— crates/glimpse-services/src/services/bluetooth/source.rs:84-93 | crates/glimpse-services/src/services/network/source.rs:106-115 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/source.rs:84` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:668— crates/glimpse-shot/src/gui/overlay.rs:668-677 | crates/glimpse-shot/src/gui/result.rs:466-475 — before extracting anything, compare `crates/glimpse-shot/src/gui/overlay.rs` and `crates/glimpse-shot/src/gui/result.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/overlay.rs:668` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:899— crates/glimpse-shot/src/gui/overlay.rs:899-908 | crates/glimpse-shot/src/gui/result.rs:633-642 — before extracting anything, compare `crates/glimpse-shot/src/gui/overlay.rs` and `crates/glimpse-shot/src/gui/result.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/overlay.rs:899` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) crates/glimpse-widgets/src/bars.rs:156— crates/glimpse-widgets/src/bars.rs:156-165 | crates/glimpse-widgets/src/sparkline.rs:191-200 — before extracting anything, compare `crates/glimpse-widgets/src/bars.rs` and `crates/glimpse-widgets/src/sparkline.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/bars.rs:156` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/glimpse-widgets/src/indicator_group/imp.rs:62— crates/glimpse-widgets/src/indicator_group/imp.rs:62-71 | crates/glimpse-widgets/src/pager/imp.rs:57-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/indicator_group/imp.rs:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/glimpse-widgets/src/scrubber/imp.rs:152— crates/glimpse-widgets/src/scrubber/imp.rs:152-161 | crates/glimpse-widgets/src/slider_row/imp.rs:272-281 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/scrubber/imp.rs:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/glimpsectl/src/commands/panel.rs:498— crates/glimpsectl/src/commands/panel.rs:498-507 | crates/glimpsectl/src/commands/status.rs:141-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) crates/glimpse-lens/src/lens.rs:289— crates/glimpse-lens/src/lens.rs:289-298 | crates/glimpse-lens/src/session.rs:454-463 — before extracting anything, compare `crates/glimpse-lens/src/lens.rs` and `crates/glimpse-lens/src/session.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-lens/src/lens.rs:289` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:1102— crates/glimpse-shot/src/gui/overlay.rs:1102-1111 | crates/glimpse-shot/src/gui/result.rs:935-944 — before extracting anything, compare `crates/glimpse-shot/src/gui/overlay.rs` and `crates/glimpse-shot/src/gui/result.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/overlay.rs:1102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/glimpsectl/src/commands/settings.rs:29— crates/glimpsectl/src/commands/settings.rs:29-38 | crates/glimpsectl/src/commands/settings.rs:157-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpsectl/src/commands/settings.rs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/glimpse-services/src/services/brightness/mod.rs:259— crates/glimpse-services/src/services/brightness/mod.rs:259-268 | crates/glimpse-services/src/services/brightness/mod.rs:271-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) crates/glimpse-wayland/src/capture/ext.rs:222— crates/glimpse-wayland/src/capture/ext.rs:222-226 | crates/glimpse-wayland/src/capture/ext.rs:263-267 — 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/glimpse-widgets/src/hero/imp.rs:50— crates/glimpse-widgets/src/hero/imp.rs:50-54 | crates/glimpse-widgets/src/notification_header/imp.rs:54-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/hero/imp.rs:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/glimpse-panel/src/applet/popover.rs:138— crates/glimpse-panel/src/applet/popover.rs:138-142 | crates/glimpse-services/src/services/exec/launcher.rs:119-123 — 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/glimpse-widgets/src/notice/imp.rs:63— crates/glimpse-widgets/src/notice/imp.rs:63-67 | crates/glimpse-widgets/src/now_playing/imp.rs:82-86 — 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/glimpse-widgets/src/shot_banner/imp.rs:22— crates/glimpse-widgets/src/shot_banner/imp.rs:22-26 | crates/glimpse-widgets/src/shot_countdown/imp.rs:32-36 — 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/glimpse-widgets/src/hero/imp.rs:56— crates/glimpse-widgets/src/hero/imp.rs:56-60 | crates/glimpse-widgets/src/notification_header/imp.rs:60-64 — 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/glimpse-widgets/src/inhibitor_list/mod.rs:109— crates/glimpse-widgets/src/inhibitor_list/mod.rs:109-115 | crates/glimpse-widgets/src/privacy_popover/mod.rs:99-103 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/inhibitor_list/mod.rs:109` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) crates/glimpse-shot/src/gui/app.rs:700— crates/glimpse-shot/src/gui/app.rs:700-704 | crates/glimpse-shot/src/gui/app.rs:710-714 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/app.rs:700` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/glimpse-shot/src/notify.rs:210— crates/glimpse-shot/src/notify.rs:210-214 | crates/glimpse-wallpaper/src/portal/notify.rs:112-116 — before extracting anything, compare `crates/glimpse-shot/src/notify.rs` and `crates/glimpse-wallpaper/src/portal/notify.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/notify.rs:210` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) crates/glimpse-panel/src/applets/exec/dom.rs:939— crates/glimpse-panel/src/applets/exec/dom.rs:939-943 | crates/glimpse-panel/src/applets/exec/dom.rs:964-968 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/exec/dom.rs:939` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/glimpse-panel/src/applets/exec/dom.rs:936` calls `set_property` and `crates/glimpse-panel/src/applets/exec/dom.rs:963` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) crates/glimpse-shot/src/gui/app.rs:487— crates/glimpse-shot/src/gui/app.rs:487-491 | crates/glimpse-shot/src/gui/app.rs:814-818 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/app.rs:487` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) sdk/sdk-go/sdk/widget.go:99— sdk/sdk-go/sdk/widget.go:99-103 | sdk/sdk-go/sdk/widget.go:257-261 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `sdk/sdk-go/sdk/widget.go:99` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Hollow method — returns a constant without doing the work crates/glimpse-agents/src/network/mod.rs:252— `cancel_get_secrets` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-agents/src/polkit/agent.rs:290— `cancel_authentication` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-dbus/src/testing/tray.rs:216— `attention_accessible_desc` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-dbus/src/testing/tray.rs:236— `x_ayatana_label_guide` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-dbus/src/testing/tray.rs:241— `x_ayatana_ordering_index` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-dbus/src/testing/tray.rs:342— `attention_icon_pixmap` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-dbus/src/testing/tray.rs:347— `attention_movie_name` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-dbus/src/testing/tray.rs:352— `item_is_menu` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-services/src/services/tray/watcher.rs:116— `protocol_version` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-services/src/services/tray/watcher.rs:182— `register_status_notifier_host` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-services/src/services/tray/watcher.rs:203— `protocol_version` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Hollow method — returns a constant without doing the work crates/glimpse-shot/src/prime.rs:5— `print` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:432— `SliderRowProps.on_move` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:433— `SliderRowProps.on_change` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:460— `EntryProps.on_change` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:461— `EntryProps.on_submit` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:473— `EntryRowProps.on_change` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:474— `EntryRowProps.on_submit` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:575— `ScaleProps.on_change` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:641— `ChoiceListProps.on_select` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:679— `CalendarProps.on_month` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:680— `CalendarProps.on_select` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpse-services/src/services/exec/tree.rs:689— `DropDownProps.on_select` is offered as a configuration-file option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
Configuration option is read nowhere crates/glimpsectl/src/cli.rs:209— `IdleCommand::Inhibit.lapse` is offered as a command-line argument option, so whoever configures the program can set it — but no production code reads it. Every value supplied for it is silently ignored. Consult it where it was meant to take effect — or, if it genuinely does nothing, remove it (or mark it deprecated and say so in its documentation) so the configuration stops advertising a setting that changes nothing.
FunctionTooLong: glimpsectl::commands::run::applets_run crates/glimpsectl/src/commands/run.rs:179— FunctionTooLong — glimpsectl::commands::run::applets_run runs 248 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 148 over it, 2.48× 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: glimpse_panel::applets::build crates/glimpse-panel/src/applets/mod.rs:55— FunctionTooLong — glimpse_panel::applets::build runs 172 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 72 over it, 1.72× 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: glimpse_dbus::clients::idle::follow_provider crates/glimpse-dbus/src/clients/idle.rs:412— FunctionTooLong — glimpse_dbus::clients::idle::follow_provider runs 144 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 44 over it, 1.44× 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: glimpsectl::run crates/glimpsectl/src/main.rs:33— FunctionTooLong — glimpsectl::run runs 134 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 34 over it, 1.34× 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: glimpse_shot::doc::wire::to_mark crates/glimpse-shot/src/doc/wire.rs:340— FunctionTooLong — glimpse_shot::doc::wire::to_mark runs 131 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 31 over it, 1.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: glimpsectl::commands::applets_author::new_with_catalog crates/glimpsectl/src/commands/applets_author.rs:198— FunctionTooLong — glimpsectl::commands::applets_author::new_with_catalog runs 129 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 29 over it, 1.29× 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: glimpse_services::services::audio::pulse::run crates/glimpse-services/src/services/audio/pulse.rs:166— FunctionTooLong — glimpse_services::services::audio::pulse::run runs 122 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 22 over it, 1.22× 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: glimpse_shot::headless::capture crates/glimpse-shot/src/headless.rs:86— FunctionTooLong — glimpse_shot::headless::capture runs 121 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 21 over it, 1.21× 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: glimpse_lens::session::connect crates/glimpse-lens/src/session.rs:316— FunctionTooLong — glimpse_lens::session::connect 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.
FunctionTooLong: host.makeHost sdk/sdk-ts/host.ts:98— FunctionTooLong — makeHost runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× 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: glimpse_dbus::clients::follower::follow_snapshots crates/glimpse-dbus/src/clients/follower.rs:175— FunctionTooLong — glimpse_dbus::clients::follower::follow_snapshots runs 104 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 4 over it, 1.04× 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.
ClassTooLong: Dom crates/glimpse-panel/src/applets/exec/dom.rs:62— ClassTooLong — 990 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 3 blocks, lines 62-1333. The bar is 400 significant lines; this is 590 over it, 2.48× 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: Run crates/glimpse-shot/src/gui/overlay.rs:100— ClassTooLong — 983 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 44 methods, 2 blocks, lines 100-1502. The bar is 400 significant lines; this is 583 over it, 2.46× 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: Exec crates/glimpse-services/src/services/exec/mod.rs:472— ClassTooLong — 915 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 3 blocks, lines 472-1699. The bar is 400 significant lines; this is 515 over it, 2.29× 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: ResultFace crates/glimpse-shot/src/gui/result.rs:65— ClassTooLong — 728 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 37 methods, 2 blocks, lines 65-1170. The bar is 400 significant lines; this is 328 over it, 1.82× 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: Network crates/glimpse-services/src/services/network/mod.rs:400— ClassTooLong — 712 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 3 blocks, lines 400-1524. The bar is 400 significant lines; this is 312 over it, 1.78× 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: App crates/glimpse-lock/src/app.rs:132— ClassTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 18 methods, 3 blocks, lines 132-906. The bar is 400 significant lines; this is 188 over it, 1.47× 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: Shell crates/glimpse-shot/src/gui/app.rs:202— ClassTooLong — 567 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 26 methods, 2 blocks, lines 202-959. The bar is 400 significant lines; this is 167 over it, 1.42× 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: Editor crates/glimpse-shot/src/gui/canvas.rs:122— ClassTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 40 methods, 2 blocks, lines 122-893. The bar is 400 significant lines; this is 149 over it, 1.37× 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: App crates/glimpse-notifications/src/app.rs:148— ClassTooLong — 477 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 3 blocks, lines 148-794. The bar is 400 significant lines; this is 77 over it, 1.19× 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: App crates/glimpse-agents/src/app.rs:36— ClassTooLong — 418 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 13 methods, 3 blocks, lines 36-730. The bar is 400 significant lines; this is 18 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: Bluetooth crates/glimpse-services/src/services/bluetooth/mod.rs:277— ClassTooLong — 416 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 3 blocks, lines 277-952. The bar is 400 significant lines; this is 16 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×11
Edited copy of a member (9 corresponding lines) crates/glimpse-widgets/src/bars.rs:283— crates/glimpse-widgets/src/bars.rs:283-291 | crates/glimpse-widgets/src/sparkline.rs:464-472 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-agents/src/main.rs:34— crates/glimpse-agents/src/main.rs:34-44 | crates/glimpse-lock/src/main.rs:46-54 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) sdk/sdk-rs/src/elements.rs:297— sdk/sdk-rs/src/elements.rs:297-305 | sdk/sdk-rs/src/elements.rs:341-350 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-widgets/src/password_prompt/imp.rs:115— crates/glimpse-widgets/src/password_prompt/imp.rs:115-123 | crates/glimpse-widgets/src/workspace_name_popover/imp.rs:47-57 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-widgets/src/audio_popover/mod.rs:239— crates/glimpse-widgets/src/audio_popover/mod.rs:239-247 | crates/glimpse-widgets/src/audio_popover/mod.rs:376-385 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-widgets/src/expander_row/imp.rs:50— crates/glimpse-widgets/src/expander_row/imp.rs:50-59 | crates/glimpse-widgets/src/row/imp.rs:178-186 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-calendar/src/services.rs:66— crates/glimpse-calendar/src/services.rs:66-76 | crates/glimpse-weather/src/services.rs:65-73 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:142— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:142-152 | crates/glimpse-widgets/src/network_popover/mod.rs:252-260 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-config/src/schema/notifications.rs:62— crates/glimpse-config/src/schema/notifications.rs:62-73 | crates/glimpse-config/src/schema/wallpaper.rs:227-235 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-services/src/service.rs:374— crates/glimpse-services/src/service.rs:374-382 | crates/glimpse-panel/src/applet/runtime.rs:654-662 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:154— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:154-162 | crates/glimpse-widgets/src/network_popover/mod.rs:239-247 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×10
Edited copy of a member (13 corresponding lines) crates/glimpse-services/src/services/battery.rs:630— crates/glimpse-services/src/services/battery.rs:630-642 | crates/glimpse-services/src/services/battery.rs:644-657 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-widgets/src/calendar/imp.rs:246— crates/glimpse-widgets/src/calendar/imp.rs:246-258 | crates/glimpse-widgets/src/indicator_group/imp.rs:33-45 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-widgets/src/printing_popover/mod.rs:103— crates/glimpse-widgets/src/printing_popover/mod.rs:103-115 | crates/glimpse-widgets/src/privacy_popover/mod.rs:70-82 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-agents/src/app.rs:766— crates/glimpse-agents/src/app.rs:766-780 | crates/glimpse-lens/src/overlay.rs:186-198 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:34— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:34-46 | crates/glimpse-widgets/src/network_popover/mod.rs:31-45 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-services/src/services/calendar.rs:459— crates/glimpse-services/src/services/calendar.rs:459-471 | crates/glimpse-services/src/services/places/mod.rs:254-266 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-agents/src/bluetooth/mod.rs:239— crates/glimpse-agents/src/bluetooth/mod.rs:239-251 | crates/glimpse-agents/src/obex/mod.rs:469-481 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-services/src/services/exec/mod.rs:323— crates/glimpse-services/src/services/exec/mod.rs:323-336 | crates/glimpse-services/src/services/exec/mod.rs:355-367 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-idle/src/idle.rs:197— crates/glimpse-idle/src/idle.rs:197-212 | crates/glimpse-idle/src/idle.rs:214-226 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/glimpse-widgets/src/artwork.rs:231— crates/glimpse-widgets/src/artwork.rs:231-243 | crates/glimpse-widgets/src/raster.rs:580-592 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×10
Edited copy of a member (8 corresponding lines) crates/glimpse-agents/src/bluetooth/mod.rs:199— crates/glimpse-agents/src/bluetooth/mod.rs:199-206 | crates/glimpse-agents/src/network/mod.rs:289-301 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-shot/src/gui/app.rs:918— crates/glimpse-shot/src/gui/app.rs:918-925 | crates/glimpse-shot/src/gui/app.rs:927-934 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-widgets/src/clipboard_popover/imp.rs:36— crates/glimpse-widgets/src/clipboard_popover/imp.rs:36-47 | crates/glimpse-widgets/src/session_popover/imp.rs:34-41 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-widgets/src/display_popover/mod.rs:43— crates/glimpse-widgets/src/display_popover/mod.rs:43-50 | crates/glimpse-widgets/src/source_list/mod.rs:37-44 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-widgets/src/display_popover/mod.rs:77— crates/glimpse-widgets/src/display_popover/mod.rs:77-84 | crates/glimpse-widgets/src/inhibitor_list/mod.rs:64-71 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-widgets/src/lib.rs:282— crates/glimpse-widgets/src/lib.rs:282-291 | crates/glimpse-widgets/src/track_card/mod.rs:95-102 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-agents/src/app.rs:641— crates/glimpse-agents/src/app.rs:641-649 | crates/glimpse-notifications/src/app.rs:138-145 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-services/src/services/printing/call.rs:113— crates/glimpse-services/src/services/printing/call.rs:113-120 | crates/glimpse-services/src/services/printing/source.rs:204-211 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-widgets/src/display_list/mod.rs:61— crates/glimpse-widgets/src/display_list/mod.rs:61-68 | crates/glimpse-widgets/src/display_popover/mod.rs:86-93 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) crates/glimpse-panel/src/applets/idle/mod.rs:45— crates/glimpse-panel/src/applets/idle/mod.rs:45-52 | crates/glimpse-panel/src/applets/notifications/indicator.rs:60-67 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×9
Edited copy of a member (12 corresponding lines) crates/glimpse-shot/src/doc/history.rs:160— crates/glimpse-shot/src/doc/history.rs:160-175 | crates/glimpse-shot/src/gui/canvas.rs:689-700 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/glimpse-lens/src/lens.rs:307— crates/glimpse-lens/src/lens.rs:307-319 | crates/glimpse-lens/src/session.rs:496-507 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/glimpse-panel/src/applets/places/render.rs:18— crates/glimpse-panel/src/applets/places/render.rs:18-29 | crates/glimpse-panel/src/applets/removable/render.rs:25-39 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/glimpse-widgets/src/shot_banner/mod.rs:26— crates/glimpse-widgets/src/shot_banner/mod.rs:26-37 | crates/glimpse-widgets/src/shot_banner/mod.rs:39-50 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/glimpse-dbus/src/testing/tray.rs:737— crates/glimpse-dbus/src/testing/tray.rs:737-748 | crates/glimpse-dbus/src/testing/tray.rs:773-784 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/glimpse-widgets/src/slider_row/imp.rs:83— crates/glimpse-widgets/src/slider_row/imp.rs:83-95 | crates/glimpse-widgets/src/slider_row/imp.rs:99-110 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/glimpse-widgets/src/network_popover/mod.rs:56— crates/glimpse-widgets/src/network_popover/mod.rs:56-68 | crates/glimpse-widgets/src/network_popover/mod.rs:110-121 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/glimpse-services/src/services/audio/pulse.rs:598— crates/glimpse-services/src/services/audio/pulse.rs:598-609 | crates/glimpse-services/src/services/audio/pulse.rs:611-622 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/glimpse-shot/src/portal.rs:90— crates/glimpse-shot/src/portal.rs:90-101 | crates/glimpse-wallpaper/src/portal.rs:194-207 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×9
Edited copy of a member (6 corresponding lines) crates/glimpse-shot/src/gui/canvas.rs:1102— crates/glimpse-shot/src/gui/canvas.rs:1102-1107 | crates/glimpse-shot/src/gui/canvas.rs:1271-1277 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/glimpse-panel/src/applets/clock/popover.rs:37— crates/glimpse-panel/src/applets/clock/popover.rs:37-42 | crates/glimpse-widgets/src/calendar/imp.rs:221-226 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/glimpse-services/src/services/mpris/mod.rs:586— crates/glimpse-services/src/services/mpris/mod.rs:586-591 | crates/glimpse-services/src/services/session.rs:134-139 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/glimpse-notifications/src/app.rs:1068— crates/glimpse-notifications/src/app.rs:1068-1073 | crates/glimpse-panel/src/applets/notifications/indicator.rs:397-403 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/glimpse-dbus/src/clients/bluez.rs:202— crates/glimpse-dbus/src/clients/bluez.rs:202-207 | crates/glimpse-dbus/src/clients/mod.rs:132-137 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/glimpse-shot/src/doc/document.rs:173— crates/glimpse-shot/src/doc/document.rs:173-178 | crates/glimpse-shot/src/headless.rs:245-250 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/glimpse-agents/src/lock.rs:40— crates/glimpse-agents/src/lock.rs:40-45 | crates/glimpse-idle/src/wayland_notify.rs:200-207 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/glimpse-widgets/src/bars.rs:173— crates/glimpse-widgets/src/bars.rs:173-178 | crates/glimpse-widgets/src/range_bar.rs:49-55 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) crates/glimpse-services/src/selection.rs:44— crates/glimpse-services/src/selection.rs:44-49 | crates/glimpse-wayland/src/selection/mod.rs:30-35 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
glimpse_shot::doc::redact::pixelate_stroke (cognitive 40) crates/glimpse-shot/src/doc/redact.rs:93— glimpse_shot::doc::redact::pixelate_stroke has cognitive complexity 40 (threshold 15). Drivers by points: loops 11 (27 pts), if/else 6 (13 pts) (nesting depth added 23). 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.
glimpse_shot::doc::redact::redact (cognitive 28) crates/glimpse-shot/src/doc/redact.rs:13— glimpse_shot::doc::redact::redact has cognitive complexity 28 (threshold 15). Drivers by points: loops 9 (28 pts) (nesting depth added 19). 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.
glimpse_shot::headless::capture (cognitive 26) crates/glimpse-shot/src/headless.rs:86— glimpse_shot::headless::capture has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 7 (12 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
glimpse_shot::cli::validate_annotate (cognitive 21) crates/glimpse-shot/src/cli.rs:497— glimpse_shot::cli::validate_annotate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 7 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_shot::doc::redact::box_blur (cognitive 19) crates/glimpse-shot/src/doc/redact.rs:204— glimpse_shot::doc::redact::box_blur has cognitive complexity 19 (threshold 15). Drivers by points: loops 7 (16 pts), match/switch 2, if/else 1 (nesting depth added 9). 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.
glimpse_shot::cli::editor_option_after (cognitive 18) crates/glimpse-shot/src/cli.rs:624— glimpse_shot::cli::editor_option_after has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 5, match/switch 2 (4 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.
glimpse_shot::cli::validate_gui (cognitive 16) crates/glimpse-shot/src/cli.rs:440— glimpse_shot::cli::validate_gui has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 7 (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.
TooManyMethods: ServiceEndpoint crates/glimpse-services/src/service.rs:91— TooManyMethods — 105 methods, declared across 23 files: exec/mod.rs (13), network/mod.rs (12), bluetooth/mod.rs (10), services/notifications.rs (9), +19 more file(s). The bar is 30 methods; this is 75 over it, 3.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: Run crates/glimpse-shot/src/gui/overlay.rs:100— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Editor crates/glimpse-shot/src/gui/canvas.rs:122— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ResultFace crates/glimpse-shot/src/gui/result.rs:65— TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LockStage crates/glimpse-widgets/src/lock_stage/imp.rs:22— TooManyMethods — 35 methods, declared across 2 files: lock_stage/mod.rs (23), lock_stage/imp.rs (12). The bar is 30 methods; this is 5 over it, 1.17× 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: ShotToolbar crates/glimpse-widgets/src/shot_toolbar/imp.rs:10— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ExpanderRow crates/glimpse-widgets/src/expander_row/imp.rs:13— TooManyMethods — 32 methods, declared across 2 files: expander_row/imp.rs (24), expander_row/mod.rs (8). The bar is 30 methods; this is 2 over it, 1.07× 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.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×7
Edited copy of a member (15 corresponding lines) crates/glimpse-shot/src/notify.rs:209— crates/glimpse-shot/src/notify.rs:209-227 | crates/glimpse-wallpaper/src/portal/notify.rs:111-125 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/glimpse-widgets/src/mpris_popover/imp.rs:102— crates/glimpse-widgets/src/mpris_popover/imp.rs:102-116 | crates/glimpse-widgets/src/popover_shell/imp.rs:182-196 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/glimpse-lock/src/app.rs:1358— crates/glimpse-lock/src/app.rs:1358-1372 | crates/glimpse-notifications/src/app.rs:1041-1056 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/glimpse-widgets/src/shot_capture_page/mod.rs:254— crates/glimpse-widgets/src/shot_capture_page/mod.rs:254-268 | crates/glimpse-widgets/src/shot_result_page/mod.rs:98-113 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/glimpse-notifications/src/app.rs:608— crates/glimpse-notifications/src/app.rs:608-622 | crates/glimpse-notifications/src/app.rs:624-640 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/glimpse-panel/src/applets/audio/indicator.rs:283— crates/glimpse-panel/src/applets/audio/indicator.rs:283-299 | crates/glimpse-panel/src/applets/bluetooth/indicator.rs:268-282 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) crates/glimpse-widgets/src/inhibitor_list/mod.rs:142— crates/glimpse-widgets/src/inhibitor_list/mod.rs:142-156 | crates/glimpsectl/src/commands/idle.rs:205-219 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×7
Edited copy of a member (10 corresponding lines) crates/glimpse-widgets/src/display_list/imp.rs:39— crates/glimpse-widgets/src/display_list/imp.rs:39-48 | crates/glimpse-widgets/src/pager/imp.rs:28-38 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/glimpse-widgets/src/places_popover/mod.rs:183— crates/glimpse-widgets/src/places_popover/mod.rs:183-192 | crates/glimpse-widgets/src/printing_popover/mod.rs:130-140 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/glimpse-widgets/src/session_popover/imp.rs:49— crates/glimpse-widgets/src/session_popover/imp.rs:49-58 | crates/glimpse-widgets/src/session_sheet/imp.rs:105-115 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/glimpse-panel/src/applet/popover.rs:144— crates/glimpse-panel/src/applet/popover.rs:144-153 | crates/glimpse-services/src/services/exec/launcher.rs:84-93 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/glimpse-widgets/src/expander_row/imp.rs:216— crates/glimpse-widgets/src/expander_row/imp.rs:216-225 | crates/glimpse-agents/src/dialog/imp.rs:74-83 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/glimpse-services/src/gamma.rs:57— crates/glimpse-services/src/gamma.rs:57-66 | crates/glimpse-services/src/selection.rs:107-116 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/glimpse-compositor-hyprland/src/main.rs:13— crates/glimpse-compositor-hyprland/src/main.rs:13-22 | crates/glimpse-compositor-niri/src/main.rs:13-22 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
glimpse_panel::applets::tray::menu::install (cognitive 28) crates/glimpse-panel/src/applets/tray/menu.rs:137— glimpse_panel::applets::tray::menu::install has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 2 (3 pts), match/switch 1 (3 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.
glimpse_panel::applets::tray::icon::choose (cognitive 24) crates/glimpse-panel/src/applets/tray/icon.rs:30— glimpse_panel::applets::tray::icon::choose has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 1 (4 pts), match/switch 1 (3 pts) (nesting depth added 16). 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.
glimpse_panel::applets::network::render::details (cognitive 21) crates/glimpse-panel/src/applets/network/render.rs:231— glimpse_panel::applets::network::render::details has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_panel::selection::run (cognitive 21) crates/glimpse-panel/src/selection/mod.rs:148— glimpse_panel::selection::run has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 2 (6 pts), boolean chains 2, loops 1 (nesting depth added 12). 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.
glimpse_panel::app::reconcile_panels (cognitive 17) crates/glimpse-panel/src/app.rs:517— glimpse_panel::app::reconcile_panels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 3 (4 pts), match/switch 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_panel::config_alert::spawn (cognitive 17) crates/glimpse-panel/src/config_alert.rs:71— glimpse_panel::config_alert::spawn has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 2 (6 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.
Duplicated block (13 lines × 2) crates/glimpse-dbus/src/clients/follower.rs:207— crates/glimpse-dbus/src/clients/follower.rs:207-219 | crates/glimpse-dbus/src/clients/idle.rs:460-472 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-dbus/src/clients/follower.rs:207` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) crates/glimpse-lens/src/lens.rs:58— crates/glimpse-lens/src/lens.rs:58-70 | crates/glimpse-lens/src/session.rs:149-161 — before extracting anything, compare `crates/glimpse-lens/src/lens.rs` and `crates/glimpse-lens/src/session.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-lens/src/lens.rs:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/glimpse-lens/src/session.rs:148` calls `default` and `crates/glimpse-lens/src/lens.rs:57` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) crates/glimpse-panel/src/applets/exec/dom.rs:1079— crates/glimpse-panel/src/applets/exec/dom.rs:1079-1091 | crates/glimpse-panel/src/applets/exec/dom.rs:1113-1125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/exec/dom.rs:1079` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/glimpse-services/src/services/bluetooth/mod.rs:487— crates/glimpse-services/src/services/bluetooth/mod.rs:487-499 | crates/glimpse-services/src/services/removable/mod.rs:324-336 — `crates/glimpse-services/src/services/bluetooth/mod.rs` and `crates/glimpse-services/src/services/removable/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/mod.rs:487` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/glimpse-shot/src/doc/wire.rs:348— crates/glimpse-shot/src/doc/wire.rs:348-360 | crates/glimpse-shot/src/doc/wire.rs:367-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) sdk/sdk-go/sdk/widget.go:273— sdk/sdk-go/sdk/widget.go:273-285 | sdk/sdk-go/sdk/widget.go:300-312 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `sdk/sdk-go/sdk/widget.go:273` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Exec::handle (cognitive 230) crates/glimpse-services/src/services/exec/mod.rs:1036— Exec::handle has cognitive complexity 230 (threshold 15). Drivers by points: if/else 75 (178 pts), boolean chains 23, match/switch 8 (18 pts), loops 4 (11 pts) (nesting depth added 120). 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.
Exec::subscriptions (cognitive 43) crates/glimpse-services/src/services/exec/mod.rs:867— Exec::subscriptions has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (25 pts), match/switch 3 (10 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Exec::refresh (cognitive 25) crates/glimpse-panel/src/applets/exec/mod.rs:139— Exec::refresh has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 5, 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.
Exec::regroup (cognitive 23) crates/glimpse-services/src/services/exec/mod.rs:572— Exec::regroup has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 3, 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.
Exec::sync_aliases (cognitive 17) crates/glimpse-services/src/services/exec/mod.rs:515— Exec::sync_aliases has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (4 pts), boolean chains 3 (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.
glimpsectl::commands::run::applets_run (cognitive 142) crates/glimpsectl/src/commands/run.rs:179— glimpsectl::commands::run::applets_run has cognitive complexity 142 (threshold 15). Drivers by points: if/else 44 (93 pts), match/switch 11 (35 pts), boolean chains 7, loops 3 (7 pts) (nesting depth added 77). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpsectl::commands::panel::applets (cognitive 49) crates/glimpsectl/src/commands/panel.rs:222— glimpsectl::commands::panel::applets has cognitive complexity 49 (threshold 15). Drivers by points: if/else 9 (26 pts), loops 7 (15 pts), match/switch 4 (5 pts), boolean chains 3 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpsectl::commands::idle::idle_inhibit_child (cognitive 29) crates/glimpsectl/src/commands/idle.rs:89— glimpsectl::commands::idle::idle_inhibit_child has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 3 (7 pts), loops 1 (2 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.
glimpsectl::commands::panel::panel_list (cognitive 26) crates/glimpsectl/src/commands/panel.rs:617— glimpsectl::commands::panel::panel_list has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 2 (6 pts), loops 2 (4 pts), boolean chains 3 (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.
glimpsectl::commands::watch::watch (cognitive 23) crates/glimpsectl/src/commands/watch.rs:7— glimpsectl::commands::watch::watch has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 2 (5 pts), loops 3 (4 pts) (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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×5
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×5
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×5
Edited copy of a member (16 corresponding lines) crates/glimpse-widgets/src/clipboard_list/imp.rs:37— crates/glimpse-widgets/src/clipboard_list/imp.rs:37-55 | crates/glimpse-widgets/src/clipboard_popover/imp.rs:55-78 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/glimpse-services/src/services/removable/mod.rs:825— crates/glimpse-services/src/services/removable/mod.rs:825-840 | crates/glimpse-services/src/services/removable/mod.rs:842-862 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/glimpse-widgets/src/raster.rs:155— crates/glimpse-widgets/src/raster.rs:155-170 | crates/glimpse-widgets/src/raster.rs:172-188 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/glimpse-services/src/services/bluetooth/mod.rs:405— crates/glimpse-services/src/services/bluetooth/mod.rs:405-420 | crates/glimpse-services/src/services/network/mod.rs:582-602 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) crates/glimpse-idle/src/services.rs:176— crates/glimpse-idle/src/services.rs:176-194 | crates/glimpse-idle/src/services.rs:279-294 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 2) crates/glimpse-idle/src/main.rs:79— crates/glimpse-idle/src/main.rs:79-89 | crates/glimpse-sunset/src/main.rs:79-89 — before extracting anything, compare `crates/glimpse-idle/src/main.rs` and `crates/glimpse-sunset/src/main.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-idle/src/main.rs:79` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:253— crates/glimpse-shot/src/gui/overlay.rs:253-263 | crates/glimpse-shot/src/gui/result.rs:1058-1068 — before extracting anything, compare `crates/glimpse-shot/src/gui/overlay.rs` and `crates/glimpse-shot/src/gui/result.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/overlay.rs:253` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-shot/src/gui/result.rs:1069` calls `is_ok`, `mark_clean` and `crates/glimpse-shot/src/gui/overlay.rs:264` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) crates/glimpse-shot/src/notify.rs:217— crates/glimpse-shot/src/notify.rs:217-227 | crates/glimpse-wallpaper/src/portal/notify.rs:115-125 — before extracting anything, compare `crates/glimpse-shot/src/notify.rs` and `crates/glimpse-wallpaper/src/portal/notify.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/notify.rs:217` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/glimpse-widgets/src/bluetooth_popover/imp.rs:108— crates/glimpse-widgets/src/bluetooth_popover/imp.rs:108-118 | crates/glimpse-widgets/src/network_popover/imp.rs:131-141 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/bluetooth_popover/imp.rs:108` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) crates/glimpse-services/src/services/brightness/mod.rs:513— crates/glimpse-services/src/services/brightness/mod.rs:513-523 | crates/glimpse-services/src/services/brightness/mod.rs:564-574 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/brightness/mod.rs:513` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
X18 · Disposal-pattern correctness· Explicit release owed and not made on every path · ×5
Explicit release owed and not made on every path sdk/sdk-rs/src/run.rs:56— `session` (line 56) is a `Session` this function owns and never releases: no `close()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Session` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends.
Explicit release owed and not made on every path crates/glimpsectl/src/commands/doctor.rs:88— `section` (line 88) is a `Section` this function owns and never releases: no `print()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Section` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends.
Explicit release owed and not made on every path crates/glimpsectl/src/commands/doctor.rs:144— `section` (line 144) is a `Section` this function owns and never releases: no `print()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Section` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends.
Explicit release owed and not made on every path crates/glimpse-widgets/src/notifications_popover/mod.rs:142— `section` (line 142) is a `Section` this function owns and never releases: no `print()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Section` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends.
Explicit release owed and not made on every path crates/glimpse-panel/src/applets/exec/dom.rs:495— `section` (line 495) is a `Section` this function owns and never releases: no `print()` on any path, and it is not handed on. Rust drops it at the end of the scope, and `Section` has no `Drop`, so what it holds is only completed by that call and is lost without it. Release it where the work ends.
App::update (cyclomatic 54) crates/glimpse-lock/src/app.rs:299— App::update has cyclomatic complexity 54 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App::ingest (cyclomatic 44) crates/glimpse-agents/src/app.rs:286— App::ingest has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
App::update (cyclomatic 29) crates/glimpse-notifications/src/app.rs:242— App::update has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
App::update (cyclomatic 19) crates/glimpse-panel/src/app.rs:181— App::update has cyclomatic complexity 19 (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.
glimpse_dbus::clients::idle::follow_provider (cognitive 85) crates/glimpse-dbus/src/clients/idle.rs:412— glimpse_dbus::clients::idle::follow_provider has cognitive complexity 85 (threshold 15). Drivers by points: match/switch 14 (50 pts), if/else 9 (31 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 59). 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.
glimpse_dbus::clients::follower::follow_snapshots (cognitive 65) crates/glimpse-dbus/src/clients/follower.rs:175— glimpse_dbus::clients::follower::follow_snapshots has cognitive complexity 65 (threshold 15). Drivers by points: if/else 10 (33 pts), match/switch 10 (27 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 41). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_dbus::clients::settings::follow (cognitive 30) crates/glimpse-dbus/src/clients/settings.rs:218— glimpse_dbus::clients::settings::follow has cognitive complexity 30 (threshold 15). Drivers by points: match/switch 6 (13 pts), if/else 3 (12 pts), loops 2 (3 pts), boolean chains 2 (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.
glimpse_dbus::clients::provider_owner (cognitive 21) crates/glimpse-dbus/src/clients/mod.rs:30— glimpse_dbus::clients::provider_owner has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (16 pts), match/switch 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_services::services::audio::pulse::run (cognitive 39) crates/glimpse-services/src/services/audio/pulse.rs:166— glimpse_services::services::audio::pulse::run has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (22 pts), match/switch 5 (12 pts), loops 3 (5 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_services::services::calendar::expand (cognitive 19) crates/glimpse-services/src/services/calendar.rs:740— glimpse_services::services::calendar::expand has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_services::services::printing::subscription::parse (cognitive 19) crates/glimpse-services/src/services/printing/subscription.rs:160— glimpse_services::services::printing::subscription::parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, 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.
glimpse_services::services::exec::catalog::expand (cognitive 17) crates/glimpse-services/src/services/exec/catalog.rs:190— glimpse_services::services::exec::catalog::expand has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 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.
glimpse_agents::obex::notify::follow (cognitive 20) crates/glimpse-agents/src/obex/notify.rs:299— glimpse_agents::obex::notify::follow has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 5 (7 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.
glimpse_agents::lock::watch (cognitive 16) crates/glimpse-agents/src/lock.rs:47— glimpse_agents::lock::watch has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (10 pts), if/else 2 (5 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.
glimpse_agents::polkit::expand_short_command (cognitive 16) crates/glimpse-agents/src/polkit/mod.rs:150— glimpse_agents::polkit::expand_short_command has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), match/switch 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_agents::polkit::helper::drive (cognitive 16) crates/glimpse-agents/src/polkit/helper.rs:244— glimpse_agents::polkit::helper::drive has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 2 (3 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.
TooManyFields: ShotToolbar crates/glimpse-widgets/src/shot_toolbar/imp.rs:10— TooManyFields — 40 stored fields beside 33 methods. The bar is 30 stored fields; this is 10 over it, 1.33× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: App crates/glimpse-lock/src/app.rs:132— TooManyFields — 37 stored fields beside 18 methods. The bar is 30 stored fields; this is 7 over it, 1.23× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: LockStage crates/glimpse-widgets/src/lock_stage/imp.rs:22— TooManyFields — 33 stored fields beside 35 methods. The bar is 30 stored fields; this is 3 over it, 1.10× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: NetworkPopover crates/glimpse-widgets/src/network_popover/imp.rs:44— TooManyFields — 31 stored fields beside 30 methods. The bar is 30 stored fields; this is 1 over it, 1.03× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×4
REDACTED
REDACTED
REDACTED
REDACTED
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) crates/glimpse-widgets/src/popover_shell/imp.rs:207— crates/glimpse-widgets/src/popover_shell/imp.rs:207-220 | crates/glimpse-widgets/src/section/imp.rs:132-142 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/glimpse-panel/src/applets/places/indicator.rs:153— crates/glimpse-panel/src/applets/places/indicator.rs:153-166 | crates/glimpse-panel/src/applets/removable/indicator.rs:197-207 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/glimpse-widgets/src/bars.rs:327— crates/glimpse-widgets/src/bars.rs:327-339 | crates/glimpse-widgets/src/sparkline.rs:434-444 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) crates/glimpse-panel/src/applets/next_event/mod.rs:30— crates/glimpse-panel/src/applets/next_event/mod.rs:30-40 | crates/glimpse-panel/src/applets/notifications/indicator.rs:48-58 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×4
Edited copies of one member (3 members, 10+ corresponding lines) crates/glimpse-widgets/src/bars.rs:252— crates/glimpse-widgets/src/bars.rs:252-262 | crates/glimpse-widgets/src/bars.rs:293-307 | crates/glimpse-widgets/src/sparkline.rs:354-363 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) crates/glimpse-services/src/services/audio/pulse.rs:896— crates/glimpse-services/src/services/audio/pulse.rs:896-905 | crates/glimpse-services/src/services/audio/pulse.rs:955-967 | crates/glimpse-services/src/services/audio/pulse.rs:975-989 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) crates/glimpse-widgets/src/inhibitor_list/imp.rs:28— crates/glimpse-widgets/src/inhibitor_list/imp.rs:28-37 | crates/glimpse-widgets/src/shot_window_list/imp.rs:43-52 | crates/glimpse-widgets/src/workspaces_popover/imp.rs:37-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) crates/glimpse-panel/src/applets/bluetooth/indicator.rs:34— crates/glimpse-panel/src/applets/bluetooth/indicator.rs:34-43 | crates/glimpse-panel/src/applets/network/indicator.rs:222-232 | crates/glimpse-panel/src/applets/printing/indicator.rs:33-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×4
Edited copies of one member (4 members, 9+ corresponding lines) crates/glimpse-panel/src/applet/mod.rs:156— crates/glimpse-panel/src/applet/mod.rs:156-164 | crates/glimpse-panel/src/applets/audio/indicator.rs:340-348 | crates/glimpse-panel/src/applets/display/indicator.rs:404-412 | crates/glimpse-panel/src/applets/privacy/indicator.rs:163-171 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) crates/glimpse-services/src/services/bluetooth/source.rs:150— crates/glimpse-services/src/services/bluetooth/source.rs:150-158 | crates/glimpse-services/src/services/network/source.rs:220-228 | crates/glimpse-services/src/services/network/source.rs:230-238 | crates/glimpse-services/src/services/removable/source.rs:182-194 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) crates/glimpse-lock/src/app.rs:1348— crates/glimpse-lock/src/app.rs:1348-1356 | crates/glimpse-notifications/src/app.rs:1058-1066 | crates/glimpse-panel/src/app.rs:456-464 | crates/glimpse-wallpaper/src/app.rs:173-183 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 9+ corresponding lines) crates/glimpse-panel/src/applets/clipboard/indicator.rs:513— crates/glimpse-panel/src/applets/clipboard/indicator.rs:513-521 | crates/glimpse-panel/src/applets/display/indicator.rs:59-67 | crates/glimpse-panel/src/applets/mpris/mod.rs:62-71 | crates/glimpse-panel/src/applets/power/mod.rs:184-194 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (15 lines × 2) crates/glimpse-panel/src/applets/exec/dom.rs:743— crates/glimpse-panel/src/applets/exec/dom.rs:743-757 | crates/glimpse-panel/src/applets/exec/dom.rs:760-774 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/exec/dom.rs:743` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:878— crates/glimpse-shot/src/gui/overlay.rs:878-892 | crates/glimpse-shot/src/gui/result.rs:614-628 — before extracting anything, compare `crates/glimpse-shot/src/gui/overlay.rs` and `crates/glimpse-shot/src/gui/result.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) crates/glimpse-widgets/src/clipboard_list/imp.rs:38— crates/glimpse-widgets/src/clipboard_list/imp.rs:38-52 | crates/glimpse-widgets/src/clipboard_popover/imp.rs:56-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/clipboard_list/imp.rs:38` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) crates/glimpse-calendar/src/main.rs:62— crates/glimpse-calendar/src/main.rs:62-76 | crates/glimpse-weather/src/main.rs:63-77 — before extracting anything, compare `crates/glimpse-calendar/src/main.rs` and `crates/glimpse-weather/src/main.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-calendar/src/main.rs:62` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) crates/glimpse-panel/src/applets/clipboard/indicator.rs:367— crates/glimpse-panel/src/applets/clipboard/indicator.rs:367-380 | crates/glimpse-shot/src/gui/result.rs:1256-1269 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) crates/glimpse-services/src/services/network/mod.rs:1409— crates/glimpse-services/src/services/network/mod.rs:1409-1422 | crates/glimpse-services/src/services/network/mod.rs:1491-1504 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:225— crates/glimpse-shot/src/gui/overlay.rs:225-238 | crates/glimpse-shot/src/gui/result.rs:1029-1042 — before extracting anything, compare `crates/glimpse-shot/src/gui/overlay.rs` and `crates/glimpse-shot/src/gui/result.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/overlay.rs:225` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) crates/glimpse-widgets/src/shot_capture_page/mod.rs:255— crates/glimpse-widgets/src/shot_capture_page/mod.rs:255-268 | crates/glimpse-widgets/src/shot_result_page/mod.rs:100-113 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/shot_result_page/mod.rs:100` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/glimpse-services/src/services/bluetooth/source.rs:218— crates/glimpse-services/src/services/bluetooth/source.rs:218-229 | crates/glimpse-services/src/services/network/source.rs:270-281 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/source.rs:218` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/glimpse-widgets/src/idle_popover/imp.rs:87— crates/glimpse-widgets/src/idle_popover/imp.rs:87-98 | crates/glimpse-widgets/src/power_popover/imp.rs:143-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/idle_popover/imp.rs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) crates/glimpse-widgets/src/workspace_list/imp.rs:29— crates/glimpse-widgets/src/workspace_list/imp.rs:29-40 | crates/glimpse-widgets/src/workspace_section/imp.rs:38-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) crates/glimpse-panel/src/main.rs:21— crates/glimpse-panel/src/main.rs:21-32 | crates/glimpse-wallpaper/src/main.rs:13-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 3) crates/glimpse-services/src/services/network/mod.rs:1381— crates/glimpse-services/src/services/network/mod.rs:1381-1387 | crates/glimpse-services/src/services/network/mod.rs:1397-1403 | crates/glimpse-services/src/services/network/mod.rs:1479-1485 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/network/mod.rs:1381` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) crates/glimpse-shot/src/doc/document.rs:241— crates/glimpse-shot/src/doc/document.rs:241-247 | crates/glimpse-shot/src/doc/redact.rs:114-120 | crates/glimpse-shot/src/render.rs:180-186 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) crates/glimpse-widgets/src/forecast/hour.rs:49— crates/glimpse-widgets/src/forecast/hour.rs:49-55 | crates/glimpse-widgets/src/notice/imp.rs:49-55 | crates/glimpse-widgets/src/placeholder/imp.rs:36-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) crates/glimpse-widgets/src/bluetooth_popover/device.rs:38— crates/glimpse-widgets/src/bluetooth_popover/device.rs:38-44 | crates/glimpse-widgets/src/network_popover/row.rs:31-37 | crates/glimpse-widgets/src/removable_popover/device.rs:43-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Off the main sequence: glimpse-config — glimpse-config: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 15 project(s), so it's rigid to change.
Off the main sequence: glimpse-utils — glimpse-utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 20 project(s), so it's rigid to change.
Off the main sequence: glimpse-widgets — glimpse-widgets: abstractness 0.01, instability 0.22, distance 0.77 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: glimpse-wayland — glimpse-wayland: 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.
Exec::handle (cyclomatic 124) crates/glimpse-services/src/services/exec/mod.rs:1036— Exec::handle has cyclomatic complexity 124 (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.
Exec::subscriptions (cyclomatic 22) crates/glimpse-services/src/services/exec/mod.rs:867— Exec::subscriptions 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.
Exec::refresh (cyclomatic 18) crates/glimpse-panel/src/applets/exec/mod.rs:139— Exec::refresh 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.
Dom::dress (cyclomatic 111) crates/glimpse-panel/src/applets/exec/dom.rs:874— Dom::dress has cyclomatic complexity 111 (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.
Dom::build (cyclomatic 42) crates/glimpse-panel/src/applets/exec/dom.rs:486— Dom::build has cyclomatic complexity 42 (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.
Dom::mount (cyclomatic 20) crates/glimpse-panel/src/applets/exec/dom.rs:316— Dom::mount 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. This is NOT this file's highest cyclomatic complexity: glimpse_panel::applets::exec::dom::element_class (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
glimpsectl::commands::run::applets_run (cyclomatic 66) crates/glimpsectl/src/commands/run.rs:179— glimpsectl::commands::run::applets_run has cyclomatic complexity 66 (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.
glimpsectl::commands::panel::applets (cyclomatic 24) crates/glimpsectl/src/commands/panel.rs:222— glimpsectl::commands::panel::applets 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.
glimpsectl::commands::idle::idle_inhibit_child (cyclomatic 17) crates/glimpsectl/src/commands/idle.rs:89— glimpsectl::commands::idle::idle_inhibit_child 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.
Network::merge (cyclomatic 39) crates/glimpse-services/src/services/network/mod.rs:918— Network::merge has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Network::handle (cyclomatic 34) crates/glimpse-services/src/services/network/mod.rs:631— Network::handle has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Network::run (cyclomatic 26) crates/glimpse-services/src/services/network/mod.rs:1298— Network::run has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
glimpse_shot::headless::capture (cyclomatic 30) crates/glimpse-shot/src/headless.rs:86— glimpse_shot::headless::capture has cyclomatic complexity 30 (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.
glimpse_shot::cli::validate_annotate (cyclomatic 17) crates/glimpse-shot/src/cli.rs:497— glimpse_shot::cli::validate_annotate 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.
glimpse_shot::doc::redact::pixelate_stroke (cyclomatic 17) crates/glimpse-shot/src/doc/redact.rs:93— glimpse_shot::doc::redact::pixelate_stroke has cyclomatic complexity 17 (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.
glimpse_dbus::clients::idle::follow_provider (cyclomatic 29) crates/glimpse-dbus/src/clients/idle.rs:412— glimpse_dbus::clients::idle::follow_provider has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
glimpse_dbus::clients::follower::follow_snapshots (cyclomatic 24) crates/glimpse-dbus/src/clients/follower.rs:175— glimpse_dbus::clients::follower::follow_snapshots 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.
glimpse_dbus::clients::settings::follow (cyclomatic 17) crates/glimpse-dbus/src/clients/settings.rs:218— glimpse_dbus::clients::settings::follow 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.
ResultFace::wire_keys (cyclomatic 23) crates/glimpse-shot/src/gui/result.rs:523— ResultFace::wire_keys has cyclomatic complexity 23 (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.
ResultFace::wire_pointer (cyclomatic 20) crates/glimpse-shot/src/gui/result.rs:339— ResultFace::wire_pointer has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ResultFace::wire (cyclomatic 16) crates/glimpse-shot/src/gui/result.rs:246— ResultFace::wire has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Editor::release (cyclomatic 19) crates/glimpse-shot/src/gui/canvas.rs:581— Editor::release 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.
Editor::cursor_at (cyclomatic 16) crates/glimpse-shot/src/gui/canvas.rs:477— Editor::cursor_at 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.
Editor::preview (cyclomatic 16) crates/glimpse-shot/src/gui/canvas.rs:752— Editor::preview 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.
Network::merge (cognitive 55) crates/glimpse-services/src/services/network/mod.rs:918— Network::merge has cognitive complexity 55 (threshold 15). Drivers by points: if/else 30 (54 pts), match/switch 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Network::handle (cognitive 38) crates/glimpse-services/src/services/network/mod.rs:631— Network::handle has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (27 pts), match/switch 4 (8 pts), boolean chains 3 (nesting depth added 19). 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.
Network::run (cognitive 26) crates/glimpse-services/src/services/network/mod.rs:1298— Network::run has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (22 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 12). 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.
glimpse_widgets::notification_image_body::bound (cognitive 22) crates/glimpse-widgets/src/notification_image_body/mod.rs:47— glimpse_widgets::notification_image_body::bound has cognitive complexity 22 (threshold 15). Drivers by points: loops 6 (18 pts), boolean chains 2, if/else 2 (nesting depth added 12). 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.
glimpse_widgets::raster::evict (cognitive 20) crates/glimpse-widgets/src/raster.rs:434— glimpse_widgets::raster::evict has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_widgets::sparkline::runs (cognitive 16) crates/glimpse-widgets/src/sparkline.rs:90— glimpse_widgets::sparkline::runs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Editor::cursor_at (cognitive 21) crates/glimpse-shot/src/gui/canvas.rs:477— Editor::cursor_at has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), match/switch 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.
Editor::release (cognitive 18) crates/glimpse-shot/src/gui/canvas.rs:581— Editor::release has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (17 pts), 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.
Editor::preview (cognitive 16) crates/glimpse-shot/src/gui/canvas.rs:752— Editor::preview has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) crates/glimpse-services/src/services/weather/met_no.rs:242— crates/glimpse-services/src/services/weather/met_no.rs:242-262 | crates/glimpse-services/src/services/weather/place.rs:87-115 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/glimpse-shot/src/doc/history.rs:108— crates/glimpse-shot/src/doc/history.rs:108-128 | crates/glimpse-shot/src/doc/history.rs:130-150 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) crates/glimpse-panel/src/applets/printing/render.rs:125— crates/glimpse-panel/src/applets/printing/render.rs:125-163 | crates/glimpse-panel/src/applets/printing/render.rs:324-344 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×3
Edited copies of one member (3 members, 13+ corresponding lines) crates/glimpse-widgets/src/places_popover/mod.rs:108— crates/glimpse-widgets/src/places_popover/mod.rs:108-120 | crates/glimpse-widgets/src/places_popover/mod.rs:122-134 | crates/glimpse-widgets/src/places_popover/mod.rs:136-148 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) crates/glimpse-services/src/services/tray/watcher.rs:46— crates/glimpse-services/src/services/tray/watcher.rs:46-59 | crates/glimpse-services/src/services/tray/watcher.rs:66-78 | crates/glimpse-services/src/services/tray/watcher.rs:85-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) crates/glimpse-panel/src/applets/audio/indicator.rs:668— crates/glimpse-panel/src/applets/audio/indicator.rs:668-681 | crates/glimpse-panel/src/applets/places/indicator.rs:119-131 | crates/glimpse-panel/src/applets/removable/indicator.rs:166-178 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×3
Edited copy of a member (5 corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:66— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:66-70 | crates/glimpse-widgets/src/network_popover/mod.rs:78-82 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) crates/glimpse-services/src/services/mpris/select.rs:9— crates/glimpse-services/src/services/mpris/select.rs:9-13 | crates/glimpse-services/src/services/notifications.rs:590-594 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) crates/glimpse-widgets/src/notification_text_body/imp.rs:113— crates/glimpse-widgets/src/notification_text_body/imp.rs:113-117 | crates/glimpse-widgets/src/row/imp.rs:106-110 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 3) crates/glimpse-services/src/services/bluetooth/source.rs:23— crates/glimpse-services/src/services/bluetooth/source.rs:23-33 | crates/glimpse-services/src/services/network/source.rs:23-33 | crates/glimpse-services/src/services/removable/source.rs:23-33 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 3) crates/glimpse-services/src/services/bluetooth/source.rs:180— crates/glimpse-services/src/services/bluetooth/source.rs:180-190 | crates/glimpse-services/src/services/network/source.rs:208-218 | crates/glimpse-services/src/services/removable/source.rs:146-156 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 3) crates/glimpse-services/src/services/bluetooth/source.rs:204— crates/glimpse-services/src/services/bluetooth/source.rs:204-214 | crates/glimpse-services/src/services/network/source.rs:256-266 | crates/glimpse-services/src/services/removable/source.rs:170-180 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 3) crates/glimpse-services/src/services/bluetooth/mod.rs:695— crates/glimpse-services/src/services/bluetooth/mod.rs:695-704 | crates/glimpse-services/src/services/removable/mod.rs:454-463 | crates/glimpse-services/src/services/removable/mod.rs:498-507 — `crates/glimpse-services/src/services/bluetooth/mod.rs` and `crates/glimpse-services/src/services/removable/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/mod.rs:695` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) crates/glimpse-services/src/services/bluetooth/source.rs:193— crates/glimpse-services/src/services/bluetooth/source.rs:193-202 | crates/glimpse-services/src/services/network/source.rs:245-254 | crates/glimpse-services/src/services/removable/source.rs:159-168 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (10 lines × 3) crates/glimpse-services/src/services/bluetooth/source.rs:217— crates/glimpse-services/src/services/bluetooth/source.rs:217-226 | crates/glimpse-services/src/services/network/source.rs:269-278 | crates/glimpse-services/src/services/removable/source.rs:183-192 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/source.rs:217` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Run::wire (cyclomatic 62) crates/glimpse-shot/src/gui/overlay.rs:556— Run::wire has cyclomatic complexity 62 (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.
Run::perform (cyclomatic 16) crates/glimpse-shot/src/gui/overlay.rs:216— Run::perform has cyclomatic complexity 16 (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.
SlotStream::read (cyclomatic 24) crates/glimpse-services/src/services/exec/spawn.rs:253— SlotStream::read has cyclomatic complexity 24 (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.
SlotStream::start (cyclomatic 16) crates/glimpse-services/src/services/exec/spawn.rs:364— SlotStream::start has cyclomatic complexity 16 (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.
glimpse_lens::lens::connect (cyclomatic 19) crates/glimpse-lens/src/lens.rs:175— glimpse_lens::lens::connect has cyclomatic complexity 19 (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.
glimpse_lens::session::connect (cyclomatic 19) crates/glimpse-lens/src/session.rs:316— glimpse_lens::session::connect has cyclomatic complexity 19 (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.
Dom::dress (cognitive 160) crates/glimpse-panel/src/applets/exec/dom.rs:874— Dom::dress has cognitive complexity 160 (threshold 15). Drivers by points: if/else 61 (133 pts), match/switch 6 (13 pts), boolean chains 12, loops 2 (nesting depth added 79). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Dom::mount (cognitive 33) crates/glimpse-panel/src/applets/exec/dom.rs:316— Dom::mount has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (18 pts), match/switch 5 (11 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App::ingest (cognitive 52) crates/glimpse-agents/src/app.rs:286— App::ingest has cognitive complexity 52 (threshold 15). Drivers by points: if/else 19 (41 pts), boolean chains 7, match/switch 2 (4 pts) (nesting depth added 24). 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.
App::update (cognitive 49) crates/glimpse-lock/src/app.rs:299— App::update has cognitive complexity 49 (threshold 15). Drivers by points: if/else 21 (40 pts), match/switch 4 (7 pts), boolean chains 2 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_idle::inhibitors::login1_observer::start (cognitive 27) crates/glimpse-idle/src/inhibitors/login1_observer.rs:134— glimpse_idle::inhibitors::login1_observer::start has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 5 (9 pts), match/switch 2 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_idle::inhibitors::screen_saver::watch_disconnects (cognitive 23) crates/glimpse-idle/src/inhibitors/screen_saver.rs:165— glimpse_idle::inhibitors::screen_saver::watch_disconnects has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 1 (5 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 14). 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.
ResultFace::wire_keys (cognitive 27) crates/glimpse-shot/src/gui/result.rs:523— ResultFace::wire_keys has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (21 pts), boolean chains 4, loops 2 (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.
ResultFace::wire_pointer (cognitive 22) crates/glimpse-shot/src/gui/result.rs:339— ResultFace::wire_pointer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 17 (19 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
glimpse_compositors::merge::apply (cognitive 25) crates/glimpse-compositors/src/merge.rs:4— glimpse_compositors::merge::apply has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 3 (5 pts), loops 2 (4 pts) (nesting depth added 13). 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.
glimpse_compositors::provider::follow (cognitive 22) crates/glimpse-compositors/src/provider.rs:132— glimpse_compositors::provider::follow has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 2 (6 pts), loops 2 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OwnedPanel::finish_units (cognitive 24) crates/glimpsectl/src/commands/dev.rs:212— OwnedPanel::finish_units has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 2 (7 pts), loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OwnedPanel::start_with (cognitive 17) crates/glimpsectl/src/commands/dev.rs:61— OwnedPanel::start_with has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 3, loops 2, boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Shell::choose_image (cognitive 22) crates/glimpse-shot/src/gui/app.rs:861— Shell::choose_image has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Shell::dispatch (cognitive 16) crates/glimpse-shot/src/gui/app.rs:345— Shell::dispatch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), match/switch 4 (6 pts), boolean chains 3 (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.
DesktopMode::handle (cognitive 20) crates/glimpse-services/src/services/desktop_mode.rs:147— DesktopMode::handle has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 2 (3 pts), boolean chains 2 (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.
DesktopMode::apply (cognitive 16) crates/glimpse-services/src/services/desktop_mode.rs:267— DesktopMode::apply has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
glimpse_lens::lens::connect (cognitive 17) crates/glimpse-lens/src/lens.rs:175— glimpse_lens::lens::connect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (4 pts), match/switch 2 (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.
glimpse_lens::session::connect (cognitive 17) crates/glimpse-lens/src/session.rs:316— glimpse_lens::session::connect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 2 (4 pts), match/switch 2 (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.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) crates/glimpse-widgets/src/mpris_popover/imp.rs:81— crates/glimpse-widgets/src/mpris_popover/imp.rs:81-98 | crates/glimpse-widgets/src/popover_shell/mod.rs:134-152 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) crates/glimpse-widgets/src/inhibitor_list/mod.rs:99— crates/glimpse-widgets/src/inhibitor_list/mod.rs:99-116 | crates/glimpse-widgets/src/privacy_popover/mod.rs:86-105 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) crates/glimpse-widgets/src/choice_list/mod.rs:63— crates/glimpse-widgets/src/choice_list/mod.rs:63-92 | crates/glimpse-widgets/src/player_list/mod.rs:67-88 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) crates/glimpse-services/src/services/bluetooth/mod.rs:369— crates/glimpse-services/src/services/bluetooth/mod.rs:369-390 | crates/glimpse-services/src/services/removable/mod.rs:243-264 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) crates/glimpsectl/src/commands/applets_author.rs:119— crates/glimpsectl/src/commands/applets_author.rs:119-142 | crates/glimpsectl/src/commands/package_manager.rs:102-125 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) crates/glimpsectl/src/commands/notifications.rs:50— crates/glimpsectl/src/commands/notifications.rs:50-73 | crates/glimpsectl/src/commands/sunset.rs:37-60 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) crates/glimpse-services/src/services/brightness/mod.rs:512— crates/glimpse-services/src/services/brightness/mod.rs:512-534 | crates/glimpse-services/src/services/brightness/mod.rs:563-581 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) crates/glimpsectl/src/commands/idle.rs:69— crates/glimpsectl/src/commands/idle.rs:69-87 | crates/glimpsectl/src/commands/settings.rs:124-142 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×2
Edited copies of one member (4 members, 11+ corresponding lines) crates/glimpse-services/src/services/battery.rs:316— crates/glimpse-services/src/services/battery.rs:316-326 | crates/glimpse-services/src/services/battery.rs:334-344 | crates/glimpse-services/src/services/session_actions.rs:233-243 | crates/glimpse-services/src/services/session_actions.rs:250-260 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 11+ corresponding lines) crates/glimpse-widgets/src/display_popover/mod.rs:193— crates/glimpse-widgets/src/display_popover/mod.rs:193-203 | crates/glimpse-widgets/src/display_popover/mod.rs:382-392 | crates/glimpse-widgets/src/player_list/mod.rs:108-119 | crates/glimpse-widgets/src/source_list/mod.rs:99-110 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) crates/glimpse-services/src/services/exec/launcher.rs:283— crates/glimpse-services/src/services/exec/launcher.rs:283-291 | crates/glimpse-services/src/services/exec/launcher.rs:293-301 | crates/glimpse-services/src/services/exec/launcher.rs:303-311 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) crates/glimpse-widgets/src/entry_row/imp.rs:80— crates/glimpse-widgets/src/entry_row/imp.rs:80-88 | crates/glimpse-widgets/src/row/imp.rs:225-234 | crates/glimpse-widgets/src/row/imp.rs:279-287 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 7+ corresponding lines) · ×2
Edited copies of one member (5 members, 7+ corresponding lines) crates/glimpse-config/src/schema/applets.rs:577— crates/glimpse-config/src/schema/applets.rs:577-583 | crates/glimpse-config/src/schema/lock.rs:77-83 | crates/glimpse-config/src/schema/notifications.rs:78-84 | crates/glimpse-config/src/schema/osd.rs:33-39 | crates/glimpse-config/src/schema/wallpaper.rs:168-174 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
Edited copies of one member (5 members, 7+ corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:131— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:131-137 | crates/glimpse-widgets/src/display_popover/mod.rs:120-126 | crates/glimpse-widgets/src/network_popover/mod.rs:223-229 | crates/glimpse-widgets/src/power_popover/mod.rs:169-175 | crates/glimpse-widgets/src/privacy_popover/mod.rs:62-68 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 4+ corresponding lines) · ×2
Edited copies of one member (4 members, 4+ corresponding lines) crates/glimpse-services/src/services/bluetooth/source.rs:46— crates/glimpse-services/src/services/bluetooth/source.rs:46-49 | crates/glimpse-services/src/services/kdeconnect/source.rs:48-51 | crates/glimpse-services/src/services/network/source.rs:46-49 | crates/glimpse-services/src/services/removable/source.rs:46-49 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) crates/glimpse-widgets/src/entry_row/imp.rs:37— crates/glimpse-widgets/src/entry_row/imp.rs:37-40 | crates/glimpse-widgets/src/row/imp.rs:322-325 | crates/glimpse-widgets/src/section/imp.rs:38-41 | crates/glimpse-widgets/src/slider_row/imp.rs:167-170 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (18 lines × 2) crates/glimpse-panel/src/applets/idle/mod.rs:65— crates/glimpse-panel/src/applets/idle/mod.rs:65-82 | crates/glimpse-panel/src/applets/power/mod.rs:215-232 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/idle/mod.rs:65` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (18 lines × 2) crates/glimpsectl/src/commands/package_manager.rs:177— crates/glimpsectl/src/commands/package_manager.rs:177-194 | crates/glimpsectl/src/commands/run.rs:30-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (17 lines × 2) crates/glimpse-panel/src/applets/display/indicator.rs:206— crates/glimpse-panel/src/applets/display/indicator.rs:206-222 | crates/glimpse-panel/src/applets/display/indicator.rs:225-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-panel/src/applets/display/indicator.rs:206` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) crates/glimpsectl/src/commands/panel.rs:231— crates/glimpsectl/src/commands/panel.rs:231-247 | crates/glimpsectl/src/commands/watch.rs:31-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 3) crates/glimpse-services/src/services/audio/mod.rs:308— crates/glimpse-services/src/services/audio/mod.rs:308-320 | crates/glimpse-services/src/services/audio/mod.rs:333-345 | crates/glimpse-services/src/services/audio/mod.rs:359-371 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/audio/mod.rs:308` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 3) crates/glimpse-notifications/src/provider.rs:142— crates/glimpse-notifications/src/provider.rs:142-154 | crates/glimpse-sunset/src/provider.rs:83-95 | crates/glimpse-weather/src/provider.rs:88-100 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-notifications/src/provider.rs:142` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) crates/glimpse-agents/src/app.rs:783— crates/glimpse-agents/src/app.rs:783-791 | crates/glimpse-notifications/src/app.rs:894-902 | crates/glimpse-shot/src/gui/overlay.rs:1731-1739 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 3) crates/glimpse-services/src/services/bluetooth/source.rs:73— crates/glimpse-services/src/services/bluetooth/source.rs:73-81 | crates/glimpse-services/src/services/network/source.rs:95-103 | crates/glimpse-services/src/services/removable/source.rs:68-76 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/source.rs:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `ctx` to `Ctx<Bluetooth>` in one and `Ctx<Network>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 4) crates/glimpse-widgets/src/notification_stack/imp.rs:45— crates/glimpse-widgets/src/notification_stack/imp.rs:45-50 | crates/glimpse-widgets/src/places_popover/imp.rs:82-87 | crates/glimpse-widgets/src/player_list/imp.rs:27-32 | crates/glimpse-widgets/src/removable_popover/imp.rs:82-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/notification_stack/imp.rs:45` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) crates/glimpse-dbus/src/clients/calendar.rs:133— crates/glimpse-dbus/src/clients/calendar.rs:133-138 | crates/glimpse-dbus/src/clients/night_light.rs:208-213 | crates/glimpse-dbus/src/clients/notifications.rs:315-320 | crates/glimpse-dbus/src/clients/weather.rs:358-363 — 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 (6 lines × 3) crates/glimpse-lock/src/app.rs:900— crates/glimpse-lock/src/app.rs:900-905 | crates/glimpse-panel/src/app.rs:363-368 | crates/glimpse-wallpaper/src/app.rs:165-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (6 lines × 3) crates/glimpse-widgets/src/bluetooth_popover/imp.rs:103— crates/glimpse-widgets/src/bluetooth_popover/imp.rs:103-108 | crates/glimpse-widgets/src/idle_popover/imp.rs:58-63 | crates/glimpse-widgets/src/network_popover/imp.rs:123-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/bluetooth_popover/imp.rs:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 9) crates/glimpse-panel/src/applets/audio/indicator.rs:683— crates/glimpse-panel/src/applets/audio/indicator.rs:683-688 | crates/glimpse-panel/src/applets/bluetooth/indicator.rs:337-342 | crates/glimpse-panel/src/applets/display/indicator.rs:549-554 | crates/glimpse-panel/src/applets/idle/mod.rs:142-148 | crates/glimpse-panel/src/applets/keyboard/indicator.rs:114-119 | crates/glimpse-panel/src/applets/places/indicator.rs:133-138 | crates/glimpse-panel/src/applets/printing/indicator.rs:199-204 | crates/glimpse-panel/src/applets/removable/indicator.rs:180-185 | crates/glimpse-panel/src/applets/weather/mod.rs:145-151 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 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 9 times.
Duplicated block (6 lines × 9) crates/glimpse-widgets/src/now_playing/imp.rs:143— crates/glimpse-widgets/src/now_playing/imp.rs:143-148 | crates/glimpse-widgets/src/scrubber/imp.rs:188-193 | crates/glimpse-widgets/src/shot_banner/imp.rs:34-39 | crates/glimpse-widgets/src/shot_capture_page/imp.rs:77-82 | crates/glimpse-widgets/src/shot_countdown/imp.rs:61-66 | crates/glimpse-widgets/src/shot_region/imp.rs:45-50 | crates/glimpse-widgets/src/shot_result_page/imp.rs:163-168 | crates/glimpse-widgets/src/shot_toolbar/imp.rs:138-143 | crates/glimpse-widgets/src/shot_window_list/imp.rs:60-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 9 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 9 times.
X12 · Unreachable branch· Statement is unreachable · ×2
Statement is unreachable — control never gets past the statement before it crates/glimpse-widgets/src/reconcile.rs:54— `widget.unparent();` follows `exit(& widget);` (line 53) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run.
Statement is unreachable — control never gets past the statement before it crates/glimpse-services/src/services/notifications.rs:1125— `if ! sides.contains(& width) || ! sides.contains(& height) { return None; }` follows `{ return None; }` (line 1122) in the same block, and control never passes that statement — it returns, breaks, continues, panics, exits or calls a function that never returns. This code cannot run for any input; rustc warns `unreachable_code` on it. Delete it, or move it before the statement that leaves if it was meant to run.
Tray::handle (cyclomatic 31) crates/glimpse-services/src/services/tray/mod.rs:265— Tray::handle has cyclomatic complexity 31 (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.
testing.render.commit (cyclomatic 31) sdk/sdk-ts/testing.ts:68— testing.render.commit has cyclomatic complexity 31 (threshold 15). Of this number, 25 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Notifications::dispatch (cyclomatic 28) crates/glimpse-services/src/services/notifications.rs:328— Notifications::dispatch has cyclomatic complexity 28 (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.
session.session (cyclomatic 28) sdk/sdk-ts/session.ts:129— session.session has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
glimpse_compositors::merge::apply (cyclomatic 25) crates/glimpse-compositors/src/merge.rs:4— glimpse_compositors::merge::apply has cyclomatic complexity 25 (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.
sdk.run (cyclomatic 23) sdk/sdk-go/sdk/run.go:32— sdk.run has cyclomatic complexity 23 (threshold 15). Of this number, 18 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AgentDialog::show (cyclomatic 22) crates/glimpse-agents/src/dialog/imp.rs:207— AgentDialog::show has cyclomatic complexity 22 (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.
Agent::defer (cyclomatic 22) crates/glimpse-agents/src/polkit/agent.rs:81— Agent::defer 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.
glimpse_services::services::audio::pulse::run (cyclomatic 22) crates/glimpse-services/src/services/audio/pulse.rs:166— glimpse_services::services::audio::pulse::run 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.
Frame::upright (cyclomatic 22) crates/glimpse-wayland/src/capture/mod.rs:103— Frame::upright has cyclomatic complexity 22 (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.
Session.reconcile (cyclomatic 22) sdk/sdk-go/sdk/session.go:152— Session.reconcile 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.
Removable::handle (cyclomatic 21) crates/glimpse-services/src/services/removable/mod.rs:306— Removable::handle has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
glimpse_sdk::run::run_inner (cyclomatic 21) sdk/sdk-rs/src/run.rs:30— glimpse_sdk::run::run_inner has cyclomatic complexity 21 (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.
Lifecycle::handle (cyclomatic 20) crates/glimpse-lock/src/lifecycle.rs:164— Lifecycle::handle has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Bluetooth::handle (cyclomatic 20) crates/glimpse-services/src/services/bluetooth/mod.rs:451— Bluetooth::handle has cyclomatic complexity 20 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AppletRuntime::update (cyclomatic 19) crates/glimpse-panel/src/applet/runtime.rs:324— AppletRuntime::update has cyclomatic complexity 19 (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.
Audio::run (cyclomatic 19) crates/glimpse-services/src/services/audio/mod.rs:239— Audio::run 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.
Printing::handle (cyclomatic 19) crates/glimpse-services/src/services/printing/mod.rs:304— Printing::handle 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.
Prefs::build (cyclomatic 19) crates/glimpse-shot/src/gui/prefs.rs:93— Prefs::build has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Session._reconcile (cyclomatic 19) sdk/sdk-py/glimpse_sdk/session.py:141— Session._reconcile 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.
sdk.clean (cyclomatic 19) sdk/sdk-go/sdk/widget.go:63— sdk.clean has cyclomatic complexity 19 (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.
wire.wireProps (cyclomatic 18) sdk/sdk-ts/wire.ts:107— wire.wireProps 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.
glimpse_agents::obex::notify::follow (cyclomatic 17) crates/glimpse-agents/src/obex/notify.rs:299— glimpse_agents::obex::notify::follow 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.
Weather::handle (cyclomatic 17) crates/glimpse-services/src/services/weather/mod.rs:340— Weather::handle 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.
OwnedPanel::start_with (cyclomatic 17) crates/glimpsectl/src/commands/dev.rs:61— OwnedPanel::start_with 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.
Session.handle (cyclomatic 17) sdk/sdk-py/glimpse_sdk/session.py:245— Session.handle has cyclomatic complexity 17 (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.
sdk.applyStructProps (cyclomatic 17) sdk/sdk-go/sdk/widget.go:299— sdk.applyStructProps 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.
Logind::follow (cyclomatic 16) crates/glimpse-lock/src/logind.rs:193— Logind::follow has cyclomatic complexity 16 (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.
DesktopMode::handle (cyclomatic 16) crates/glimpse-services/src/services/desktop_mode.rs:147— DesktopMode::handle 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.
CameraSource::next (cyclomatic 16) crates/glimpse-services/src/services/privacy/source.rs:180— CameraSource::next 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.
Sparkline::snapshot (cyclomatic 16) crates/glimpse-widgets/src/sparkline.rs:221— Sparkline::snapshot 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.
Run::wire (cognitive 62) crates/glimpse-shot/src/gui/overlay.rs:556— Run::wire has cognitive complexity 62 (threshold 15). Drivers by points: if/else 39 (46 pts), boolean chains 12, match/switch 3 (4 pts) (nesting depth added 8). 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.
testing.render.commit (cognitive 61) sdk/sdk-ts/testing.ts:68— testing.render.commit has cognitive complexity 61 (threshold 15). Drivers by points: if/else 20 (45 pts), loops 5 (9 pts), boolean chains 6, ternaries 1 (nesting depth added 29). Of this number, 55 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
session.session (cognitive 52) sdk/sdk-ts/session.ts:129— session.session has cognitive complexity 52 (threshold 15). Drivers by points: if/else 7 (22 pts), ternaries 4 (15 pts), loops 4 (7 pts), error handling 2 (5 pts), boolean chains 3 (nesting depth added 32). Of this number, 49 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sdk.run (cognitive 42) sdk/sdk-go/sdk/run.go:32— sdk.run has cognitive complexity 42 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 4 (6 pts), match/switch 3 (6 pts), jumps 2, boolean chains 1 (nesting depth added 20). Of this number, 35 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_sdk::run::run_inner (cognitive 39) sdk/sdk-rs/src/run.rs:30— glimpse_sdk::run::run_inner has cognitive complexity 39 (threshold 15). Drivers by points: match/switch 6 (16 pts), if/else 5 (14 pts), loops 5 (9 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.
Frame::upright (cognitive 34) crates/glimpse-wayland/src/capture/mod.rs:103— Frame::upright has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 4 (9 pts), loops 4 (8 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sdk.oversized (cognitive 32) sdk/sdk-go/sdk/widget.go:113— sdk.oversized has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 4 (10 pts), match/switch 2 (3 pts) (nesting depth added 20). 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.
sdk.applyStructProps (cognitive 32) sdk/sdk-go/sdk/widget.go:299— sdk.applyStructProps has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (28 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.
Session.reconcile (cognitive 32) sdk/sdk-go/sdk/session.go:152— Session.reconcile has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (22 pts), loops 6, boolean chains 2, match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Notifications::dispatch (cognitive 31) crates/glimpse-services/src/services/notifications.rs:328— Notifications::dispatch has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 3 (5 pts), loops 2 (4 pts), boolean chains 3 (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.
_Connection._dispatch (cognitive 31) sdk/sdk-py/glimpse_sdk/runtime.py:102— _Connection._dispatch has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 4 (7 pts), error handling 1 (3 pts), boolean chains 2 (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.
Audio::run (cognitive 27) crates/glimpse-services/src/services/audio/mod.rs:239— Audio::run has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (26 pts), match/switch 1 (nesting depth added 13). 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.
CameraSource::next (cognitive 27) crates/glimpse-services/src/services/privacy/source.rs:180— CameraSource::next has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (14 pts), match/switch 4 (10 pts), boolean chains 2, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Sparkline::snapshot (cognitive 27) crates/glimpse-widgets/src/sparkline.rs:221— Sparkline::snapshot has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 5 (9 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.
sdk.clean (cognitive 27) sdk/sdk-go/sdk/widget.go:63— sdk.clean has cognitive complexity 27 (threshold 15). Drivers by points: loops 4 (11 pts), if/else 4 (10 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 14). 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.
Session._reconcile (cognitive 26) sdk/sdk-py/glimpse_sdk/session.py:141— Session._reconcile has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 3, boolean chains 2, ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
glimpse_settings_daemon::provider::start (cognitive 25) crates/glimpse-settings-daemon/src/provider.rs:95— glimpse_settings_daemon::provider::start has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (22 pts), 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.
Tray::handle (cognitive 24) crates/glimpse-services/src/services/tray/mod.rs:265— Tray::handle has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 11). 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.
Watch::next (cognitive 23) crates/glimpse-config/src/watch.rs:351— Watch::next has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (8 pts), match/switch 2 (6 pts) (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.
Agent::defer (cognitive 22) crates/glimpse-agents/src/polkit/agent.rs:81— Agent::defer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 3 (6 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.
Logind::follow (cognitive 22) crates/glimpse-lock/src/logind.rs:193— Logind::follow has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 6 (14 pts), if/else 2 (7 pts), loops 1 (nesting depth added 13). 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.
Weather::handle (cognitive 22) crates/glimpse-services/src/services/weather/mod.rs:340— Weather::handle has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 3 (5 pts) (nesting depth added 12). 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.
AgentDialog::show (cognitive 21) crates/glimpse-agents/src/dialog/imp.rs:207— AgentDialog::show has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 4, match/switch 1 (nesting depth added 1). 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.
Prefs::build (cognitive 21) crates/glimpse-shot/src/gui/prefs.rs:93— Prefs::build has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), match/switch 4, loops 2, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Session.Rebuild (cognitive 21) sdk/sdk-go/sdk/session.go:237— Session.Rebuild has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). Of this number, 18 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wire.wireProps (cognitive 21) sdk/sdk-ts/wire.ts:107— wire.wireProps has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, loops 1, ternaries 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.
testing.render (cognitive 21) sdk/sdk-ts/testing.ts:26— testing.render has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), error handling 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 8). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 159). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
Reader::next (cognitive 20) crates/glimpse-config/src/watch.rs:235— Reader::next has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Session.Handle (cognitive 19) sdk/sdk-go/sdk/session.go:291— Session.Handle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (18 pts), 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.
Lifecycle::backend_ready (cognitive 18) crates/glimpse-lock/src/lifecycle.rs:241— Lifecycle::backend_ready has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Printing::handle (cognitive 18) crates/glimpse-services/src/services/printing/mod.rs:304— Printing::handle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 2 (3 pts), loops 1 (2 pts) (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.
Session::reconcile_children (cognitive 17) sdk/sdk-rs/src/session.rs:183— Session::reconcile_children has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), match/switch 3 (6 pts), loops 4, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
W.__init__ (cognitive 17) sdk/sdk-py/glimpse_sdk/widget.py:13— W.__init__ has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (10 pts), boolean chains 3, if/else 2 (3 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.
glimpse_config::load::load_files (cognitive 16) crates/glimpse-config/src/load.rs:370— glimpse_config::load::load_files has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), match/switch 3 (6 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SlotStream::read (cognitive 16) crates/glimpse-services/src/services/exec/spawn.rs:253— SlotStream::read has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 6 (9 pts), if/else 4 (7 pts) (nesting depth added 6). 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.
Removable::handle (cognitive 16) crates/glimpse-services/src/services/removable/mod.rs:306— Removable::handle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), match/switch 2 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
glimpse_wallpaper::portal::notify::changed (cognitive 16) crates/glimpse-wallpaper/src/portal/notify.rs:127— glimpse_wallpaper::portal::notify::changed has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 3 (9 pts), if/else 2 (6 pts), loops 1 (nesting depth added 10). 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.
sdk.appendStructValues (cognitive 16) sdk/sdk-go/sdk/widget.go:272— sdk.appendStructValues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 3, 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.
cli.render::walk (cognitive 16) website/scripts/cli.mjs:40— cli.render::walk has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 3 (4 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyFunctions: glimpse_config::load crates/glimpse-config/src/load.rs:78— TooManyFunctions — 42 free functions. The bar is 30 free functions; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: app.rs ↔ indicator.rs crates/glimpse-panel/src/app.rs:1— `crates/glimpse-panel/src/app.rs` and `crates/glimpse-panel/src/applets/bluetooth/indicator.rs` change together 58% of the time (7 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 7 shared commits counted here, the most recent 3 are `2c082789` Drop dialog channel and raise; use prompt_entry; `c3035d61` Add raise command and skip gating; `3649b645` Fix Gtk.Stack interpolation and Bluetooth pairing — run `git show` on any of them.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) crates/glimpse-calendar/src/main.rs:31— crates/glimpse-calendar/src/main.rs:31-76 | crates/glimpse-idle/src/main.rs:33-92 | crates/glimpse-settings-daemon/src/main.rs:32-83 | crates/glimpse-sunset/src/main.rs:32-92 | crates/glimpse-weather/src/main.rs:30-77 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/glimpse-calendar/src/main.rs:19— crates/glimpse-calendar/src/main.rs:19-29 | crates/glimpse-idle/src/main.rs:20-31 | crates/glimpse-sunset/src/main.rs:19-30 | crates/glimpse-weather/src/main.rs:18-28 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (117 corresponding lines) · ×1
Edited copy of a member (117 corresponding lines) crates/glimpse-lens/src/lens.rs:182— crates/glimpse-lens/src/lens.rs:182-298 | crates/glimpse-lens/src/session.rs:323-463 — These two members are one piece of code written twice and then edited apart: 117 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (68 corresponding lines) · ×1
Edited copy of a member (68 corresponding lines) crates/glimpse-shot/src/gui/overlay.rs:216— crates/glimpse-shot/src/gui/overlay.rs:216-287 | crates/glimpse-shot/src/gui/result.rs:1024-1091 — These two members are one piece of code written twice and then edited apart: 68 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) crates/glimpse-services/src/services/battery.rs:447— crates/glimpse-services/src/services/battery.rs:447-498 | crates/glimpse-services/src/services/session_actions.rs:273-312 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (39 corresponding lines) · ×1
Edited copy of a member (39 corresponding lines) crates/glimpse-lens/src/lens.rs:48— crates/glimpse-lens/src/lens.rs:48-86 | crates/glimpse-lens/src/session.rs:138-176 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×1
Edited copy of a member (45 corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/imp.rs:130— crates/glimpse-widgets/src/bluetooth_popover/imp.rs:130-174 | crates/glimpse-widgets/src/network_popover/imp.rs:152-217 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) crates/glimpse-lens/src/lens.rs:96— crates/glimpse-lens/src/lens.rs:96-142 | crates/glimpse-lens/src/session.rs:186-229 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/mod.rs:234— crates/glimpse-widgets/src/bluetooth_popover/mod.rs:234-264 | crates/glimpse-widgets/src/network_popover/mod.rs:321-356 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×1
Edited copy of a member (30 corresponding lines) crates/glimpse-compositor-hyprland/src/hyprland/outputs.rs:193— crates/glimpse-compositor-hyprland/src/hyprland/outputs.rs:193-228 | crates/glimpse-wayland/src/wire.rs:123-152 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) crates/glimpse-services/src/services/brightness/mod.rs:367— crates/glimpse-services/src/services/brightness/mod.rs:367-398 | crates/glimpse-services/src/services/brightness/mod.rs:423-454 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 24+ corresponding lines) · ×1
Edited copies of one member (3 members, 24+ corresponding lines) crates/glimpse-services/src/services/bluetooth/source.rs:95— crates/glimpse-services/src/services/bluetooth/source.rs:95-124 | crates/glimpse-services/src/services/network/source.rs:117-140 | crates/glimpse-services/src/services/removable/source.rs:90-113 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) crates/glimpse-notifications/src/main.rs:28— crates/glimpse-notifications/src/main.rs:28-54 | crates/glimpse-panel/src/main.rs:34-64 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) crates/glimpse-services/src/services/bluetooth/mod.rs:683— crates/glimpse-services/src/services/bluetooth/mod.rs:683-713 | crates/glimpse-services/src/services/removable/mod.rs:436-472 | crates/glimpse-services/src/services/removable/mod.rs:482-516 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) crates/glimpse-services/src/services/bluetooth/source.rs:72— crates/glimpse-services/src/services/bluetooth/source.rs:72-93 | crates/glimpse-services/src/services/network/source.rs:94-115 | crates/glimpse-services/src/services/removable/source.rs:67-88 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 23+ corresponding lines) · ×1
Edited copies of one member (4 members, 23+ corresponding lines) crates/glimpse-widgets/src/bluetooth_popover/imp.rs:102— crates/glimpse-widgets/src/bluetooth_popover/imp.rs:102-128 | crates/glimpse-widgets/src/display_popover/imp.rs:99-127 | crates/glimpse-widgets/src/network_popover/imp.rs:122-150 | crates/glimpse-widgets/src/notifications_popover/imp.rs:57-79 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) crates/glimpse-widgets/src/bars.rs:141— crates/glimpse-widgets/src/bars.rs:141-169 | crates/glimpse-widgets/src/sparkline.rs:171-204 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) crates/glimpse-agents/src/agents.rs:37— crates/glimpse-agents/src/agents.rs:37-66 | crates/glimpse-agents/src/obex/mod.rs:319-344 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) crates/glimpse-services/src/services/audio/pulse.rs:550— crates/glimpse-services/src/services/audio/pulse.rs:550-572 | crates/glimpse-services/src/services/audio/pulse.rs:574-596 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) crates/glimpse-services/src/services/bluetooth/source.rs:160— crates/glimpse-services/src/services/bluetooth/source.rs:160-177 | crates/glimpse-services/src/services/network/source.rs:188-205 | crates/glimpse-services/src/services/removable/source.rs:126-143 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) crates/glimpse-services/src/services/audio/pulse.rs:869— crates/glimpse-services/src/services/audio/pulse.rs:869-888 | crates/glimpse-services/src/services/audio/pulse.rs:925-947 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) crates/glimpse-panel/src/applets/audio/indicator.rs:310— crates/glimpse-panel/src/applets/audio/indicator.rs:310-330 | crates/glimpse-panel/src/applets/bluetooth/indicator.rs:293-313 | crates/glimpse-panel/src/applets/printing/indicator.rs:109-133 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 16+ corresponding lines) · ×1
Edited copies of one member (4 members, 16+ corresponding lines) crates/glimpse-widgets/src/calendar_popover/imp.rs:46— crates/glimpse-widgets/src/calendar_popover/imp.rs:46-61 | crates/glimpse-widgets/src/idle_popover/imp.rs:57-72 | crates/glimpse-widgets/src/power_popover/imp.rs:92-111 | crates/glimpse-widgets/src/shot_capture_page/imp.rs:49-66 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) crates/glimpse-services/src/services/places/sources.rs:175— crates/glimpse-services/src/services/places/sources.rs:175-188 | crates/glimpse-services/src/services/places/sources.rs:190-203 | crates/glimpse-services/src/services/places/sources.rs:205-217 | crates/glimpse-services/src/services/places/sources.rs:219-231 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) crates/glimpse-widgets/src/indicator/mod.rs:73— crates/glimpse-widgets/src/indicator/mod.rs:73-85 | crates/glimpse-widgets/src/indicator/mod.rs:87-98 | crates/glimpse-widgets/src/notification_header/mod.rs:25-36 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) crates/glimpse-widgets/src/places_popover/imp.rs:81— crates/glimpse-widgets/src/places_popover/imp.rs:81-92 | crates/glimpse-widgets/src/player_list/imp.rs:26-38 | crates/glimpse-widgets/src/removable_popover/imp.rs:81-96 | crates/glimpse-widgets/src/tray_strip/imp.rs:37-53 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 8+ corresponding lines) · ×1
Edited copies of one member (5 members, 8+ corresponding lines) crates/glimpse-widgets/src/entry_row/imp.rs:181— crates/glimpse-widgets/src/entry_row/imp.rs:181-188 | crates/glimpse-widgets/src/hero/imp.rs:99-106 | crates/glimpse-widgets/src/notification_card/imp.rs:273-283 | crates/glimpse-widgets/src/row/imp.rs:120-127 | crates/glimpse-widgets/src/slider_row/imp.rs:322-329 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) crates/glimpse-services/src/services/bluetooth/source.rs:56— crates/glimpse-services/src/services/bluetooth/source.rs:56-70 | crates/glimpse-services/src/services/network/source.rs:56-70 | crates/glimpse-services/src/services/removable/source.rs:51-65 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 10+ corresponding lines) · ×1
Edited copies of one member (7 members, 10+ corresponding lines) crates/glimpse-services/src/services/bluetooth/source.rs:126— crates/glimpse-services/src/services/bluetooth/source.rs:126-136 | crates/glimpse-services/src/services/bluetooth/source.rs:138-148 | crates/glimpse-services/src/services/network/source.rs:142-152 | crates/glimpse-services/src/services/network/source.rs:154-163 | crates/glimpse-services/src/services/network/source.rs:165-174 | crates/glimpse-services/src/services/network/source.rs:176-186 | crates/glimpse-services/src/services/removable/source.rs:115-124 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) crates/glimpse-agents/src/main.rs:22— crates/glimpse-agents/src/main.rs:22-32 | crates/glimpse-lock/src/main.rs:33-44 | crates/glimpse-notifications/src/main.rs:16-26 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 10+ corresponding lines) · ×1
Edited copies of one member (6 members, 10+ corresponding lines) crates/glimpse-widgets/src/entry_row/imp.rs:53— crates/glimpse-widgets/src/entry_row/imp.rs:53-63 | crates/glimpse-widgets/src/expander_row/imp.rs:63-72 | crates/glimpse-widgets/src/expander_row/imp.rs:76-85 | crates/glimpse-widgets/src/expander_row/imp.rs:89-98 | crates/glimpse-widgets/src/expander_row/imp.rs:159-168 | crates/glimpse-widgets/src/slider_row/imp.rs:49-59 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) sdk/sdk-py/glimpse_sdk/elements.py:136— sdk/sdk-py/glimpse_sdk/elements.py:136-152 | sdk/sdk-py/glimpse_sdk/elements.py:375-392 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (8 members, 8+ corresponding lines) · ×1
Edited copies of one member (8 members, 8+ corresponding lines) crates/glimpse-widgets/src/choice_list/imp.rs:39— crates/glimpse-widgets/src/choice_list/imp.rs:39-46 | crates/glimpse-widgets/src/clipboard_list/imp.rs:57-64 | crates/glimpse-widgets/src/display_list/imp.rs:50-57 | crates/glimpse-widgets/src/forecast/imp.rs:65-73 | crates/glimpse-widgets/src/inhibitor_list/imp.rs:39-46 | crates/glimpse-widgets/src/player_list/imp.rs:40-47 | crates/glimpse-widgets/src/source_list/imp.rs:39-46 | crates/glimpse-widgets/src/workspace_list/imp.rs:42-49 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×1
Edited copies of one member (3 members, 4+ corresponding lines) crates/glimpse-widgets/src/notification_header/imp.rs:89— crates/glimpse-widgets/src/notification_header/imp.rs:89-92 | crates/glimpse-widgets/src/shot_countdown/imp.rs:44-48 | crates/glimpse-widgets/src/status_island/imp.rs:37-40 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×1
Edited copies of one member (4 members, 10+ corresponding lines) crates/glimpse-panel/src/applets/audio/indicator.rs:386— crates/glimpse-panel/src/applets/audio/indicator.rs:386-396 | crates/glimpse-panel/src/applets/bluetooth/render.rs:185-195 | crates/glimpse-panel/src/applets/places/render.rs:43-53 | crates/glimpse-panel/src/applets/removable/render.rs:41-50 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) crates/glimpse-panel/src/applets/idle/mod.rs:137— crates/glimpse-panel/src/applets/idle/mod.rs:137-140 | crates/glimpse-panel/src/applets/power/mod.rs:116-119 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 7+ corresponding lines) · ×1
Edited copies of one member (4 members, 7+ corresponding lines) crates/glimpse-widgets/src/clipboard_list/mod.rs:368— crates/glimpse-widgets/src/clipboard_list/mod.rs:368-374 | crates/glimpse-widgets/src/inhibitor_list/mod.rs:76-82 | crates/glimpse-widgets/src/shot_window_list/mod.rs:51-57 | crates/glimpse-widgets/src/workspace_list/mod.rs:66-72 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (30 lines × 2) crates/glimpse-notifications/src/app.rs:1089— crates/glimpse-notifications/src/app.rs:1089-1118 | crates/glimpse-panel/src/applets/notifications/render.rs:111-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (20–21 lines × 4) crates/glimpse-calendar/src/main.rs:43— crates/glimpse-calendar/src/main.rs:43-62 | crates/glimpse-idle/src/main.rs:54-74 | crates/glimpse-sunset/src/main.rs:54-74 | crates/glimpse-weather/src/main.rs:44-63 — before extracting anything, compare `crates/glimpse-calendar/src/main.rs` and `crates/glimpse-idle/src/main.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-calendar/src/main.rs:43` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–18 lines × 3) crates/glimpse-services/src/services/bluetooth/source.rs:107— crates/glimpse-services/src/services/bluetooth/source.rs:107-124 | crates/glimpse-services/src/services/network/source.rs:126-140 | crates/glimpse-services/src/services/removable/source.rs:99-113 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/source.rs:107` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) crates/glimpse-services/src/services/audio/pulse.rs:551— crates/glimpse-services/src/services/audio/pulse.rs:551-569 | crates/glimpse-services/src/services/audio/pulse.rs:575-593 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/audio/pulse.rs:551` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `info` to `&SinkInfo` in one and `&SourceInfo` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13–16 lines × 2) crates/glimpse-services/src/services/audio/mod.rs:242— crates/glimpse-services/src/services/audio/mod.rs:242-257 | crates/glimpse-services/src/services/audio/mod.rs:267-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/audio/mod.rs:242` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) crates/glimpse-services/src/services/bluetooth/mod.rs:370— crates/glimpse-services/src/services/bluetooth/mod.rs:370-385 | crates/glimpse-services/src/services/removable/mod.rs:244-259 — `crates/glimpse-services/src/services/bluetooth/mod.rs` and `crates/glimpse-services/src/services/removable/mod.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 39 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/mod.rs:370` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 5) crates/glimpse-calendar/src/main.rs:48— crates/glimpse-calendar/src/main.rs:48-62 | crates/glimpse-idle/src/main.rs:60-74 | crates/glimpse-settings-daemon/src/main.rs:51-65 | crates/glimpse-sunset/src/main.rs:60-74 | crates/glimpse-weather/src/main.rs:49-63 — before extracting anything, compare `crates/glimpse-calendar/src/main.rs` and `crates/glimpse-idle/src/main.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-calendar/src/main.rs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) crates/glimpse-services/src/services/bluetooth/source.rs:164— crates/glimpse-services/src/services/bluetooth/source.rs:164-177 | crates/glimpse-services/src/services/network/source.rs:192-205 | crates/glimpse-services/src/services/removable/source.rs:130-143 — `crates/glimpse-services/src/services/bluetooth/source.rs` and `crates/glimpse-services/src/services/network/source.rs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 122 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/bluetooth/source.rs:164` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) crates/glimpse-notifications/src/services.rs:49— crates/glimpse-notifications/src/services.rs:49-59 | crates/glimpse-panel/src/services.rs:109-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-notifications/src/services.rs:49` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 4) crates/glimpse-calendar/src/main.rs:20— crates/glimpse-calendar/src/main.rs:20-29 | crates/glimpse-idle/src/main.rs:21-31 | crates/glimpse-sunset/src/main.rs:20-30 | crates/glimpse-weather/src/main.rs:19-28 — before extracting anything, compare `crates/glimpse-calendar/src/main.rs` and `crates/glimpse-idle/src/main.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-weather/src/main.rs:32` calls `init_locale` and `crates/glimpse-calendar/src/main.rs:33` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5–10 lines × 3) crates/glimpse-lens/src/session.rs:333— crates/glimpse-lens/src/session.rs:333-342 | crates/glimpse-lens/src/session.rs:344-353 | crates/glimpse-lens/src/session.rs:354-358 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-lens/src/session.rs:333` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 2) crates/glimpse-shot/src/gui/overlay.rs:607— crates/glimpse-shot/src/gui/overlay.rs:607-616 | crates/glimpse-shot/src/gui/result.rs:403-411 — before extracting anything, compare `crates/glimpse-shot/src/gui/overlay.rs` and `crates/glimpse-shot/src/gui/result.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 89 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-shot/src/gui/overlay.rs:607` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8–9 lines × 3) crates/glimpse-idle/src/main.rs:77— crates/glimpse-idle/src/main.rs:77-84 | crates/glimpse-settings-daemon/src/main.rs:68-76 | crates/glimpse-sunset/src/main.rs:77-84 — before extracting anything, compare `crates/glimpse-idle/src/main.rs` and `crates/glimpse-sunset/src/main.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 74 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-idle/src/main.rs:77` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 5) crates/glimpse-services/src/services/bluetooth/call.rs:16— crates/glimpse-services/src/services/bluetooth/call.rs:16-22 | crates/glimpse-services/src/services/bluetooth/call.rs:24-30 | crates/glimpse-services/src/services/kdeconnect/source.rs:184-190 | crates/glimpse-services/src/services/removable/call.rs:8-14 | crates/glimpse-services/src/services/removable/call.rs:16-22 — there are 5 copies across 3 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 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/kdeconnect/source.rs:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) crates/glimpse-widgets/src/inhibitor_list/imp.rs:29— crates/glimpse-widgets/src/inhibitor_list/imp.rs:29-36 | crates/glimpse-widgets/src/shot_window_list/imp.rs:44-51 | crates/glimpse-widgets/src/workspaces_popover/imp.rs:38-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 4) crates/glimpse-services/src/services/battery.rs:317— crates/glimpse-services/src/services/battery.rs:317-323 | crates/glimpse-services/src/services/battery.rs:335-341 | crates/glimpse-services/src/services/battery.rs:358-364 | crates/glimpse-services/src/services/session_actions.rs:251-257 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-services/src/services/battery.rs:317` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 11) crates/glimpse-widgets/src/mpris_popover/imp.rs:46— crates/glimpse-widgets/src/mpris_popover/imp.rs:46-51 | crates/glimpse-widgets/src/next_event_popover/imp.rs:51-56 | crates/glimpse-widgets/src/notification_stack/imp.rs:45-50 | crates/glimpse-widgets/src/places_popover/imp.rs:82-87 | crates/glimpse-widgets/src/player_list/imp.rs:27-32 | crates/glimpse-widgets/src/printing_popover/imp.rs:70-75 | crates/glimpse-widgets/src/privacy_popover/imp.rs:55-60 | crates/glimpse-widgets/src/removable_popover/imp.rs:82-87 | crates/glimpse-widgets/src/session_sheet/imp.rs:106-111 | crates/glimpse-widgets/src/shot_toolbar/imp.rs:105-110 | crates/glimpse-widgets/src/workspace_name_popover/imp.rs:48-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 11 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 11 times. Read the line range as the matched WINDOW rather than a finished unit: at `crates/glimpse-widgets/src/mpris_popover/imp.rs:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/glimpse-widgets/src/places_popover/imp.rs:89` calls `builder`, `build` and `crates/glimpse-widgets/src/session_sheet/imp.rs:113` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 3) sdk/sdk-py/glimpse_sdk/elements.py:136— sdk/sdk-py/glimpse_sdk/elements.py:136-151 | sdk/sdk-py/glimpse_sdk/elements.py:306-321 | sdk/sdk-py/glimpse_sdk/elements.py:375-390 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `sdk/sdk-py/glimpse_sdk/elements.py:136` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the node:test suite in sdk/sdk-ts/ ran but wrote no lcov report. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Skeleton type — most members are unfinished crates/glimpse-panel/src/applet/runtime.rs:669— `impl AppletHandle` has 4 unfinished methods out of 5 — a scaffolded type that was never implemented.
Unfinished branch — a todo!() / unimplemented!() arm in a real function crates/glimpse-services/src/services/exec/catalog.rs:138— `entry_of` does real work, but one of its branches is `Err` with a "not implemented" message — a case that was never written, and a panic the first time it is reached. Implement the case, or return an error that says why it is not handled.
P12 · CI test-gate honesty· Test suite runs only after the merge · ×1
Test suite runs only after the merge — `REDACTED`, `REDACTED`, `REDACTED`, `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
Duplicated block (6 lines × 2 locations) sdk/sdk-ts/testing.ts:108— sdk/sdk-ts/testing.ts:108 · sdk/sdk-ts/testing.ts:134 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (5 lines × 2 locations) sdk/sdk-ts/testing.ts:97— sdk/sdk-ts/testing.ts:97 · sdk/sdk-ts/testing.ts:112 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function session (cyclomatic 29, cognitive 58) sdk/sdk-ts/session.ts:129— session has cyclomatic complexity 29 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function commit (cyclomatic 24, cognitive 54) sdk/sdk-ts/testing.ts:68— commit has cyclomatic complexity 24 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function wireProps (cyclomatic 18, cognitive 27) sdk/sdk-ts/wire.ts:107— wireProps has cyclomatic complexity 18 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function dispatchEvent (cyclomatic 14, cognitive 14) sdk/sdk-ts/session.ts:85— dispatchEvent has cyclomatic complexity 14 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
SC1 · Supply-chain hygiene· JavaScript dependencies are not locked · ×1
JavaScript dependencies are not locked sdk/examples/todo/package.json:5— sdk/examples/todo/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
X2 · Cancellation propagation· Function without context.Context · ×1
Function without context.Context: run sdk/sdk-go/sdk/run.go:32— `run` calls `net.Dial(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Interpolated log message defeats structured logging crates/glimpse-weather/src/main.rs:24— `error!` at line 24 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/glimpse-wallpaper/src/main.rs:20— `error!` at line 20 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/glimpse-wallpaper/src/surface.rs:301— `warn!` 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: `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/glimpse-sunset/src/main.rs:26— `error!` at line 26 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/glimpse-shot/src/headless.rs:327— `warn!` at line 327 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/glimpse-shot/src/hold.rs:132— `warn!` at line 132 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/glimpse-shot/src/main.rs:128— `warn!` at line 128 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/glimpse-shot/src/notify.rs:63— `warn!` at line 63 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/glimpse-shot/src/notify.rs:184— `warn!` at line 184 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/glimpse-shot/src/gui/app.rs:107— `warn!` at line 107 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/glimpse-shot/src/gui/app.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/glimpse-shot/src/gui/app.rs:180— `debug!` at line 180 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/glimpse-shot/src/gui/app.rs:434— `warn!` at line 434 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/glimpse-shot/src/gui/app.rs:442— `warn!` at line 442 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/glimpse-shot/src/gui/app.rs:1116— `warn!` at line 1116 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/glimpse-shot/src/gui/mod.rs:39— `warn!` at line 39 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/glimpse-shot/src/gui/overlay.rs:268— `warn!` at line 268 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/glimpse-shot/src/gui/overlay.rs:1419— `warn!` at line 1419 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/glimpse-shot/src/gui/prefs.rs:246— `warn!` at line 246 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/glimpse-shot/src/gui/prefs.rs:290— `warn!` at line 290 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/glimpse-shot/src/gui/prefs.rs:294— `warn!` at line 294 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/glimpse-shot/src/gui/result.rs:498— `warn!` at line 498 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/glimpse-shot/src/gui/result.rs:508— `warn!` at line 508 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/glimpse-shot/src/gui/result.rs:1142— `warn!` at line 1142 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/glimpse-shot/src/gui/result.rs:1216— `debug!` at line 1216 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`.
Documentation: no build, run or usage example crates/glimpse-agents/README.md:1— `glimpse-agents` is a binary crate (`src/main.rs`) and neither `crates/glimpse-agents/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-calendar/README.md:1— `glimpse-calendar` is a binary crate (`src/main.rs`) and neither `crates/glimpse-calendar/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-compositor-hyprland/README.md:1— `glimpse-compositor-hyprland` is a binary crate (`src/main.rs`) and neither `crates/glimpse-compositor-hyprland/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-compositor-niri/README.md:1— `glimpse-compositor-niri` is a binary crate (`src/main.rs`) and neither `crates/glimpse-compositor-niri/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-compositors/README.md:1— `glimpse-compositors` is a published crate (`[package]` without `publish = false`) and neither `crates/glimpse-compositors/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-dbus/README.md:1— `glimpse-dbus` is a published crate (`[package]` without `publish = false`) and neither `crates/glimpse-dbus/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-idle/README.md:1— `glimpse-idle` is a binary crate (`src/main.rs`) and neither `crates/glimpse-idle/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-lens/README.md:1— `glimpse-lens` is a binary crate (`[[bin]]` in `Cargo.toml`) and neither `crates/glimpse-lens/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-lock/README.md:1— `glimpse-lock` is a binary crate (`src/main.rs`) and neither `crates/glimpse-lock/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-notifications/README.md:1— `glimpse-notifications` is a binary crate (`src/main.rs`) and neither `crates/glimpse-notifications/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-panel/README.md:1— `glimpse-panel` is a binary crate (`src/main.rs`) and neither `crates/glimpse-panel/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-services/README.md:1— `glimpse-services` is a published crate (`[package]` without `publish = false`) and neither `crates/glimpse-services/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-settings-daemon/README.md:1— `glimpse-settings-daemon` is a binary crate (`src/main.rs`) and neither `crates/glimpse-settings-daemon/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-sunset/README.md:1— `glimpse-sunset` is a binary crate (`src/main.rs`) and neither `crates/glimpse-sunset/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-wallpaper/README.md:1— `glimpse-wallpaper` is a binary crate (`src/main.rs`) and neither `crates/glimpse-wallpaper/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-wayland/README.md:1— `glimpse-wayland` is a published crate (`[package]` without `publish = false`) and neither `crates/glimpse-wayland/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no build, run or usage example crates/glimpse-weather/README.md:1— `glimpse-weather` is a binary crate (`src/main.rs`) and neither `crates/glimpse-weather/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Silent fallback default on Err crates/glimpse-agents/src/obex/notify.rs:226— `update` turns every `Err` into `Update::default()` — 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/glimpse-agents/src/polkit/agent.rs:493— `real_names` turns every `Err` into `HashMap::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/glimpse-dbus/src/clients/applet_host.rs:8— `panel_app_id` turns every `Err` into `"me.aresa.GlimpsePanel".to_owned()` — 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/glimpse-dbus/src/clients/network_manager.rs:460— `decode_ip4_config` turns every `Err` into `Ip4ConfigProperties::default()` — 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/glimpse-dbus/src/clients/status_notifier_item.rs:150— `pixmaps` 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/glimpse-services/src/services/kdeconnect/source.rs:276— `loaded_plugins` 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/glimpse-services/src/services/privacy/source.rs:253— `holders` 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/glimpse-services/src/services/tray/watcher.rs:477— `vanished` 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/glimpse-shot/src/adapters/screens.rs:148— `geometries` turns every `Err` into `Some(HashMap::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.
Duplicated predicate crates/glimpse-panel/src/applets/tray/menu.rs:53— `child.submenu || !child.children.is_empty()` appears character-identically in 2 files — crates/glimpse-panel/src/applets/tray/menu.rs, crates/glimpse-services/src/services/tray/menu.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/glimpse-lock/src/app.rs:1403— `geometry.width() <= 0 || geometry.height() <= 0` appears character-identically in 2 files — crates/glimpse-lock/src/app.rs, crates/glimpse-wallpaper/src/surface.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/glimpse-lens/src/lens.rs:312— `other != index && surface.lens.hovered()` appears character-identically in 2 files — crates/glimpse-lens/src/lens.rs, crates/glimpse-lens/src/session.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/glimpse-widgets/src/session_popover/mod.rs:55— `row.get_visible() == state.visible && row.is_sensitive() == state.enabled && row.subtitle().as_deref() == state.subtitle.as_deref()` appears character-identically in 2 files — crates/glimpse-widgets/src/session_popover/mod.rs, crates/glimpse-widgets/src/session_sheet/mod.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/glimpse-agents/src/bluetooth/tests.rs:652— `seen.len() >= count || Instant::now() >= deadline` appears character-identically in 2 files — crates/glimpse-agents/src/bluetooth/tests.rs, crates/glimpse-agents/src/obex/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.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×4
Projects may be oversized for their cohesion crates/glimpse-widgets/Cargo.toml:1— `crates/glimpse-widgets` (28005 LoC, 255 module-visible types across 79 directories) overshoots its size bounds. 4 of 29 build unit(s) (Cargo, Go, Python, npm) overshoot their size bounds, lowering Project Cohesion to 7.3/10. 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.
Projects may be oversized for their cohesion crates/glimpse-services/Cargo.toml:1— `crates/glimpse-services` (40241 LoC, 446 module-visible types across 17 directories) overshoots its size bounds. 4 of 29 build unit(s) (Cargo, Go, Python, npm) overshoot their size bounds, lowering Project Cohesion to 7.3/10. 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.
Projects may be oversized for their cohesion crates/glimpse-panel/Cargo.toml:1— `crates/glimpse-panel` (30816 LoC, 140 module-visible types across 27 directories) overshoots its size bounds. 4 of 29 build unit(s) (Cargo, Go, Python, npm) overshoot their size bounds, lowering Project Cohesion to 7.3/10. 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.
Projects may be oversized for their cohesion crates/glimpse-dbus/Cargo.toml:1— `crates/glimpse-dbus` (10995 LoC, 200 module-visible types across 3 directories) overshoots its size bounds. 4 of 29 build unit(s) (Cargo, Go, Python, npm) overshoot their size bounds, lowering Project Cohesion to 7.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 1 of 661 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 661 of the 958 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: crates/glimpsectl/src/commands/applets/tests.rs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Orphaned file crates/glimpsectl/src/commands/applets/tests.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
No dependency-update automation sdk/examples/todo/package.json:5— `sdk/examples/todo/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all functions that make a request accept a context.Context · ×1
Not all functions that make a request accept a context.Context — Only 0/1 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×1
Diagnostic log message is built whether or not it is wanted crates/glimpse-panel/src/components/panel.rs:254— `tracing::debug!` at line 254 is called with an argument built by `self.applets.iter().filter(|slot|slot.handle.is_some()).count()` (line 258), whose cost grows with the collection it walks. Rust evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because tracing::debug! is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `log_enabled!`/`tracing::enabled!` test, no debug flag, no `cfg(debug_assertions)`, and the work is in the argument itself, not deferred into a field the subscriber formats or a closure the formatter calls.
Silent fallback default in catch sdk/sdk-ts/hooks.ts:70— `readStateFile` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Outdated: ammonia — `ammonia` is locked at 4.1.8 but 4.2.5 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/glimpse-utils/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ammonia` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.6.6 but 4.6.8 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: clap_complete — `clap_complete` is locked at 4.6.11 but 4.6.12 is the current stable release on crates.io, and it already satisfies the `"4.6.11"` requirement declared in crates/glimpsectl/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap_complete` and commit the updated REDACTED.
Outdated: config — `config` is locked at 0.15.25 but 0.15.27 is the current stable release on crates.io, and it already satisfies the `"0.15.25"` requirement declared in crates/glimpse-config/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p config` and commit the updated REDACTED.
Outdated: gio — `gio` is locked at 0.22.8 but 0.22.11 is the current stable release on crates.io, and it already satisfies the `"0.22"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p gio` and commit the updated REDACTED.
Outdated: gio-unix — `gio-unix` is locked at 0.22.8 but 0.22.11 is the current stable release on crates.io, and it already satisfies the `"0.22"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p gio-unix` and commit the updated REDACTED.
Outdated: glib — `glib` is locked at 0.22.8 but 0.22.11 is the current stable release on crates.io, and it already satisfies the `"0.22"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p glib` and commit the updated REDACTED.
Outdated: gtk4 — `gtk4` is locked at 0.11.4 but 0.11.5 is the current stable release on crates.io, and it already satisfies the `"0.11"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p gtk4` and commit the updated REDACTED.
Outdated: icalendar — `icalendar` is locked at 0.17.13 but 0.17.17 is the current stable release on crates.io, and it already satisfies the `"0.17.13"` requirement declared in crates/glimpse-services/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p icalendar` and commit the updated REDACTED.
Outdated: iso8601 — `iso8601` is locked at 0.6.5 but 0.6.6 is the current stable release on crates.io, and it already satisfies the `"0.6.5"` requirement declared in crates/glimpse-services/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p iso8601` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.189 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2.189"` requirement declared in crates/glimpse-config/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
Outdated: notify — `notify` is locked at 8.2.0 but 8.2.2 is the current stable release on crates.io, and it already satisfies the `"8.2"` requirement declared in crates/glimpse-config/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: pam-client2 — `pam-client2` is locked at 0.5.5 but 0.5.6 is the current stable release on crates.io, and it already satisfies the `"0.5.5"` requirement declared in crates/glimpse-lock/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p pam-client2` and commit the updated REDACTED.
Outdated: reqwest — `reqwest` is locked at 0.13.4 but 0.13.5 is the current stable release on crates.io, and it already satisfies the `"0.13"` requirement declared in crates/glimpse-services/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p reqwest` and commit the updated REDACTED.
Outdated: rustix — `rustix` is locked at 1.1.4 but 1.1.6 is the current stable release on crates.io, and it already satisfies the `"1.1.4"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustix` and commit the updated REDACTED.
Outdated: schemars — `schemars` is locked at 1.2.2 but 1.2.3 is the current stable release on crates.io, and it already satisfies the `"1.2.2"` requirement declared in crates/glimpse-config/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p schemars` and commit the updated REDACTED.
Outdated: serde_json — `serde_json` is locked at 1.0.151 but 1.0.154 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/glimpse-compositor-hyprland/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.20 but 2.0.21 is the current stable release on crates.io, and it already satisfies the `"2.0.20"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p thiserror` and commit the updated REDACTED.
Outdated: tokio — `tokio` is locked at 1.53.1 but 1.54.1 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio` and commit the updated REDACTED.
Outdated: tokio-util — `tokio-util` is locked at 0.7.19 but 0.7.20 is the current stable release on crates.io, and it already satisfies the `"0.7"` requirement declared in crates/glimpse-dbus/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p tokio-util` and commit the updated REDACTED.
Outdated: toml — `toml` is locked at 1.1.4+spec-1.1.0 but 1.2.1+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"1.1"` requirement declared in crates/glimpse-config/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml` and commit the updated REDACTED.
Outdated: toml_edit — `toml_edit` is locked at 0.25.13+spec-1.1.0 but 0.25.19+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"0.25"` requirement declared in crates/glimpse-config/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml_edit` and commit the updated REDACTED.
Outdated: zeroize — `zeroize` is locked at 1.9.0 but 1.9.1 is the current stable release on crates.io, and it already satisfies the `"1.9.0"` requirement declared in crates/glimpse-agents/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zeroize` and commit the updated REDACTED.
Outdated: zip — `zip` is locked at 9.0.4 but 9.6.1 is the current stable release on crates.io, and it already satisfies the `"9"` requirement declared in crates/glimpsectl/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zip` 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. semgrep could not parse 6 file(s) — `sdk/sdk-py/glimpse_sdk/applet.py`, `sdk/sdk-py/glimpse_sdk/context.py`, `sdk/sdk-py/glimpse_sdk/runtime.py`, `sdk/sdk-py/glimpse_sdk/session.py`, `sdk/sdk-py/glimpse_sdk/widget.py`, … (+1 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e95e-c4c5-7ead-be72-2856adaa20cd · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 77 · Warnings: 824 · Recommendations: 84 · Info: 24 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 11:57 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.