Public report of atuinsh/atuin, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 26 October 2026, 02:26 UTC · Survey ID cd_9785cbd3f34f4f1da023be92c8a8e9b0
atuinsh/atuin
Measured 26 October 2026, 02:20 UTC, at code version fbbb486
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Down 3 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 181,450 lines of product code in 15 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Code Health, 47
Findings by how serious they are
93 critical471 serious106 minor
12 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 02:20 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
76of 76 dimensions measured by tools.
613of 670 findings point to an exact file and line, so you can open each one in the code. The other 57 concern the repository as a whole, such as missing documentation.
76dimensions across 8 lenses, read from 181,450 lines of product code in 15 projects.
atuinsh/atuin falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 57 out of 100 and is rated Adequate, and all 93 of its critical findings are security problems.
Code Health, at 47, is the weakest lens and counts most in the score. The best first step is turning on missing-value checks, worth about 6 points. Recording design decisions comes next, worth about 2 points. Raising Code Health to 70 would lift the score to about 64.
Forty-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen passwords or keys in the code and nine in the code's history are open to anyone who can read the repository, and thirteen weaknesses in the code could be used by an attacker. Pinning each tool to an exact version, replacing each exposed password or key and fixing the weaknesses the scanner points to would close these risks. The five unsafe settings in infrastructure or container files need changing to safe values. The two pipeline steps that run downloads without checking them need each download checked against a known checksum first.
The product code is 181,450 lines, about €180,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 34 findings
These 34 critical or serious findings were in the previous survey, on 11 October 2026, and are gone from this one.
€59,000 to €290,000, for 978 to 3,102 hours of work, about 1.2 person-years for 1 to 3 engineers
Difficulty of the problem
Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 57. 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: 181,450 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
The findings name the configuration each number was taken from and, for the assertions, the files that hold them.
Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €180,000 to build again, about 1.2 person-years of work. Its weakest lens is Code Health, at 47 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph 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.
492 modules, with 1187 dependencies between them. 4 loops run through 98 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 452 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.
atuin_ai.tools uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_ai.tools, while a change to atuin_ai.tools can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_ai.tools uses a module listed above it, which is the healthy direction.
8→30 atuin_ai.tools uses atuin_client.historypart of a loop✕
Connections
1 pair of types, where a type in atuin_ai.tools uses a type in atuin_client.history.
atuin_ai.tools uses atuin_client.history, so a change to atuin_client.history can break atuin_ai.tools, while a change to atuin_ai.tools can't break atuin_client.history.
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.
8→31 atuin_ai.tools uses atuin_client.databasepart of a loop✕
Connections
1 pair of types, where a type in atuin_ai.tools uses a type in atuin_client.database.
atuin_ai.tools uses atuin_client.database, so a change to atuin_client.database can break atuin_ai.tools, while a change to atuin_ai.tools can't break atuin_client.database.
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.
atuin_common.harnesstools.rehydrate uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_common.harnesstools.rehydrate, while a change to atuin_common.harnesstools.rehydrate can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_common.harnesstools.rehydrate uses a module listed above it, which is the healthy direction.
9→33 atuin_common.harnesstools.rehydrate uses atuin.logs.heldpart of a loop✕
Connections
1 pair of types, where a type in atuin_common.harnesstools.rehydrate uses a type in atuin.logs.held.
atuin_common.harnesstools.rehydrate uses atuin.logs.held, so a change to atuin.logs.held can break atuin_common.harnesstools.rehydrate, while a change to atuin_common.harnesstools.rehydrate can't break atuin.logs.held.
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.
atuin_ai.tui.app uses atuin_ai.fsm.events, so a change to atuin_ai.fsm.events can break atuin_ai.tui.app, while a change to atuin_ai.tui.app can't break atuin_ai.fsm.events.
Position
Below the diagonal: atuin_ai.tui.app uses a module listed above it, which is the healthy direction.
atuin_ai.tui.app uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_ai.tui.app, while a change to atuin_ai.tui.app can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_ai.tui.app uses a module listed above it, which is the healthy direction.
atuin_ai.tui.app uses atuin_ai.tools, so a change to atuin_ai.tools can break atuin_ai.tui.app, while a change to atuin_ai.tui.app can't break atuin_ai.tools.
Position
Below the diagonal: atuin_ai.tui.app uses a module listed above it, which is the healthy direction.
atuin_client.settings uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_client.settings, while a change to atuin_client.settings can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_client.settings uses a module listed above it, which is the healthy direction.
atuin_client.settings uses atuin_ai.tools, so a change to atuin_ai.tools can break atuin_client.settings, while a change to atuin_client.settings can't break atuin_ai.tools.
Position
Below the diagonal: atuin_client.settings uses a module listed above it, which is the healthy direction.
11→30 atuin_client.settings uses atuin_client.historypart of a loop✕
Connections
1 pair of types, where a type in atuin_client.settings uses a type in atuin_client.history.
atuin_client.settings uses atuin_client.history, so a change to atuin_client.history can break atuin_client.settings, while a change to atuin_client.settings can't break atuin_client.history.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→31 atuin_client.settings uses atuin_client.databasepart of a loop✕
Connections
1 pair of types, where a type in atuin_client.settings uses a type in atuin_client.database.
atuin_client.settings uses atuin_client.database, so a change to atuin_client.database can break atuin_client.settings, while a change to atuin_client.settings can't break atuin_client.database.
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.
atuin_common.harnesstools.sync uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_common.harnesstools.sync, while a change to atuin_common.harnesstools.sync can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_common.harnesstools.sync uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.sync uses atuin_common.harnesstools.sync.liveness, so a change to atuin_common.harnesstools.sync.liveness can break atuin_common.harnesstools.sync, while a change to atuin_common.harnesstools.sync can't break atuin_common.harnesstools.sync.liveness.
Position
Below the diagonal: atuin_common.harnesstools.sync uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.sync uses atuin_common.harnesstools.rehydrate, so a change to atuin_common.harnesstools.rehydrate can break atuin_common.harnesstools.sync, while a change to atuin_common.harnesstools.sync can't break atuin_common.harnesstools.rehydrate.
Position
Below the diagonal: atuin_common.harnesstools.sync uses a module listed above it, which is the healthy direction.
atuin.command.client.search.interactive uses atuin_ai.fsm.events, so a change to atuin_ai.fsm.events can break atuin.command.client.search.interactive, while a change to atuin.command.client.search.interactive can't break atuin_ai.fsm.events.
Position
Below the diagonal: atuin.command.client.search.interactive uses a module listed above it, which is the healthy direction.
atuin.command.client.search.interactive uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin.command.client.search.interactive, while a change to atuin.command.client.search.interactive can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin.command.client.search.interactive uses a module listed above it, which is the healthy direction.
atuin.command.client.search.interactive uses atuin_client.settings, so a change to atuin_client.settings can break atuin.command.client.search.interactive, while a change to atuin.command.client.search.interactive can't break atuin_client.settings.
Position
Below the diagonal: atuin.command.client.search.interactive uses a module listed above it, which is the healthy direction.
13→30 atuin.command.client.search.interactive uses atuin_client.historypart of a loop✕
Connections
4 pairs of types, where a type in atuin.command.client.search.interactive uses a type in atuin_client.history.
atuin.command.client.search.interactive uses atuin_client.history, so a change to atuin_client.history can break atuin.command.client.search.interactive, while a change to atuin.command.client.search.interactive can't break atuin_client.history.
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.
13→31 atuin.command.client.search.interactive uses atuin_client.databasepart of a loop✕
Connections
2 pairs of types, where a type in atuin.command.client.search.interactive uses a type in atuin_client.database.
atuin.command.client.search.interactive uses atuin_client.database, so a change to atuin_client.database can break atuin.command.client.search.interactive, while a change to atuin.command.client.search.interactive can't break atuin_client.database.
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.
13→38 atuin.command.client.search.interactive uses atuin.command.client.search.inspector.browserpart of a loop✕
Connections
1 pair of types, where a type in atuin.command.client.search.interactive uses a type in atuin.command.client.search.inspector.browser.
atuin.command.client.search.interactive uses atuin.command.client.search.inspector.browser, so a change to atuin.command.client.search.inspector.browser can break atuin.command.client.search.interactive, while a change to atuin.command.client.search.interactive can't break atuin.command.client.search.inspector.browser.
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.
atuin_common.harnesstools uses atuin_common.harnesstools.sync.liveness, so a change to atuin_common.harnesstools.sync.liveness can break atuin_common.harnesstools, while a change to atuin_common.harnesstools can't break atuin_common.harnesstools.sync.liveness.
Position
Below the diagonal: atuin_common.harnesstools uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools uses atuin_common.sync.blocking_pool, so a change to atuin_common.sync.blocking_pool can break atuin_common.harnesstools, while a change to atuin_common.harnesstools can't break atuin_common.sync.blocking_pool.
Position
Below the diagonal: atuin_common.harnesstools uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools uses atuin_common.harnesstools.rehydrate, so a change to atuin_common.harnesstools.rehydrate can break atuin_common.harnesstools, while a change to atuin_common.harnesstools can't break atuin_common.harnesstools.rehydrate.
Position
Below the diagonal: atuin_common.harnesstools uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools uses atuin_common.harnesstools.sync, so a change to atuin_common.harnesstools.sync can break atuin_common.harnesstools, while a change to atuin_common.harnesstools can't break atuin_common.harnesstools.sync.
Position
Below the diagonal: atuin_common.harnesstools uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.model uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_client.ai_session.model, while a change to atuin_client.ai_session.model can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_client.ai_session.model uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.model uses atuin_common.harnesstools.rehydrate, so a change to atuin_common.harnesstools.rehydrate can break atuin_client.ai_session.model, while a change to atuin_client.ai_session.model can't break atuin_common.harnesstools.rehydrate.
Position
Below the diagonal: atuin_client.ai_session.model uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.model uses atuin_common.harnesstools, so a change to atuin_common.harnesstools can break atuin_client.ai_session.model, while a change to atuin_client.ai_session.model can't break atuin_common.harnesstools.
Position
Below the diagonal: atuin_client.ai_session.model uses a module listed above it, which is the healthy direction.
15→35 atuin_client.ai_session.model uses atuin_ai.tools.session.readpart of a loop✕
Connections
1 pair of types, where a type in atuin_client.ai_session.model uses a type in atuin_ai.tools.session.read.
atuin_client.ai_session.model uses atuin_ai.tools.session.read, so a change to atuin_ai.tools.session.read can break atuin_client.ai_session.model, while a change to atuin_client.ai_session.model can't break atuin_ai.tools.session.read.
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.
atuin_ai.resume_tui.catchup uses atuin_common.harnesstools.sync, so a change to atuin_common.harnesstools.sync can break atuin_ai.resume_tui.catchup, while a change to atuin_ai.resume_tui.catchup can't break atuin_common.harnesstools.sync.
Position
Below the diagonal: atuin_ai.resume_tui.catchup uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.catchup uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_ai.resume_tui.catchup, while a change to atuin_ai.resume_tui.catchup can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_ai.resume_tui.catchup uses a module listed above it, which is the healthy direction.
16→33 atuin_ai.resume_tui.catchup uses atuin.logs.heldpart of a loop✕
Connections
1 pair of types, where a type in atuin_ai.resume_tui.catchup uses a type in atuin.logs.held.
atuin_ai.resume_tui.catchup uses atuin.logs.held, so a change to atuin.logs.held can break atuin_ai.resume_tui.catchup, while a change to atuin_ai.resume_tui.catchup can't break atuin.logs.held.
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.
atuin_ai.resume_tui.source uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_ai.resume_tui.source, while a change to atuin_ai.resume_tui.source can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_ai.resume_tui.source uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.source uses atuin_common.harnesstools.sync, so a change to atuin_common.harnesstools.sync can break atuin_ai.resume_tui.source, while a change to atuin_ai.resume_tui.source can't break atuin_common.harnesstools.sync.
Position
Below the diagonal: atuin_ai.resume_tui.source uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.source uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_ai.resume_tui.source, while a change to atuin_ai.resume_tui.source can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_ai.resume_tui.source uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.render uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_ai.resume_tui.render, while a change to atuin_ai.resume_tui.render can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_ai.resume_tui.render uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.render uses atuin_client.settings, so a change to atuin_client.settings can break atuin_ai.resume_tui.render, while a change to atuin_ai.resume_tui.render can't break atuin_client.settings.
Position
Below the diagonal: atuin_ai.resume_tui.render uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.render uses atuin.command.client.search.interactive, so a change to atuin.command.client.search.interactive can break atuin_ai.resume_tui.render, while a change to atuin_ai.resume_tui.render can't break atuin.command.client.search.interactive.
Position
Below the diagonal: atuin_ai.resume_tui.render uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.render uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_ai.resume_tui.render, while a change to atuin_ai.resume_tui.render can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_ai.resume_tui.render uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.render uses atuin_ai.resume_tui.source, so a change to atuin_ai.resume_tui.source can break atuin_ai.resume_tui.render, while a change to atuin_ai.resume_tui.render can't break atuin_ai.resume_tui.source.
Position
Below the diagonal: atuin_ai.resume_tui.render uses a module listed above it, which is the healthy direction.
18→24 atuin_ai.resume_tui.render uses atuin_common.io.line_readerpart of a loop✕
Connections
2 pairs of types, where a type in atuin_ai.resume_tui.render uses a type in atuin_common.io.line_reader.
atuin_ai.resume_tui.render uses atuin_common.io.line_reader, so a change to atuin_common.io.line_reader can break atuin_ai.resume_tui.render, while a change to atuin_ai.resume_tui.render can't break atuin_common.io.line_reader.
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.
18→35 atuin_ai.resume_tui.render uses atuin_ai.tools.session.readpart of a loop✕
Connections
1 pair of types, where a type in atuin_ai.resume_tui.render uses a type in atuin_ai.tools.session.read.
atuin_ai.resume_tui.render uses atuin_ai.tools.session.read, so a change to atuin_ai.tools.session.read can break atuin_ai.resume_tui.render, while a change to atuin_ai.resume_tui.render can't break atuin_ai.tools.session.read.
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.
18→38 atuin_ai.resume_tui.render uses atuin.command.client.search.inspector.browserpart of a loop✕
Connections
1 pair of types, where a type in atuin_ai.resume_tui.render uses a type in atuin.command.client.search.inspector.browser.
atuin_ai.resume_tui.render uses atuin.command.client.search.inspector.browser, so a change to atuin.command.client.search.inspector.browser can break atuin_ai.resume_tui.render, while a change to atuin_ai.resume_tui.render can't break atuin.command.client.search.inspector.browser.
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.
atuin_ai.resume_tui.worker uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_ai.resume_tui.worker, while a change to atuin_ai.resume_tui.worker can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_ai.resume_tui.worker uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.worker uses atuin_ai.resume_tui.source, so a change to atuin_ai.resume_tui.source can break atuin_ai.resume_tui.worker, while a change to atuin_ai.resume_tui.worker can't break atuin_ai.resume_tui.source.
Position
Below the diagonal: atuin_ai.resume_tui.worker uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.continuation uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_common.harnesstools.continuation, while a change to atuin_common.harnesstools.continuation can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_common.harnesstools.continuation uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.continuation uses atuin_common.harnesstools.rehydrate, so a change to atuin_common.harnesstools.rehydrate can break atuin_common.harnesstools.continuation, while a change to atuin_common.harnesstools.continuation can't break atuin_common.harnesstools.rehydrate.
Position
Below the diagonal: atuin_common.harnesstools.continuation uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.continuation uses atuin_common.harnesstools, so a change to atuin_common.harnesstools can break atuin_common.harnesstools.continuation, while a change to atuin_common.harnesstools.continuation can't break atuin_common.harnesstools.
Position
Below the diagonal: atuin_common.harnesstools.continuation uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.continuation uses atuin_ai.resume_tui.catchup, so a change to atuin_ai.resume_tui.catchup can break atuin_common.harnesstools.continuation, while a change to atuin_common.harnesstools.continuation can't break atuin_ai.resume_tui.catchup.
Position
Below the diagonal: atuin_common.harnesstools.continuation uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_common.harnesstools.sync.liveness, so a change to atuin_common.harnesstools.sync.liveness can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_common.harnesstools.sync.liveness.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_common.harnesstools.rehydrate, so a change to atuin_common.harnesstools.rehydrate can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_common.harnesstools.rehydrate.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_common.harnesstools.sync, so a change to atuin_common.harnesstools.sync can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_common.harnesstools.sync.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_common.harnesstools, so a change to atuin_common.harnesstools can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_common.harnesstools.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_ai.resume_tui.catchup, so a change to atuin_ai.resume_tui.catchup can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_ai.resume_tui.catchup.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_ai.resume_tui.source, so a change to atuin_ai.resume_tui.source can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_ai.resume_tui.source.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.resumer uses atuin_common.harnesstools.continuation, so a change to atuin_common.harnesstools.continuation can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_common.harnesstools.continuation.
Position
Below the diagonal: atuin_ai.resume_tui.resumer uses a module listed above it, which is the healthy direction.
21→22 atuin_ai.resume_tui.resumer uses atuin_ai.resume_tuipart of a loop✕
Connections
2 pairs of types, where a type in atuin_ai.resume_tui.resumer uses a type in atuin_ai.resume_tui.
atuin_ai.resume_tui.resumer uses atuin_ai.resume_tui, so a change to atuin_ai.resume_tui can break atuin_ai.resume_tui.resumer, while a change to atuin_ai.resume_tui.resumer can't break atuin_ai.resume_tui.
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.
atuin_ai.resume_tui uses atuin_ai.fsm.events, so a change to atuin_ai.fsm.events can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_ai.fsm.events.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui uses atuin_client.settings, so a change to atuin_client.settings can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_client.settings.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui uses atuin.command.client.search.interactive, so a change to atuin.command.client.search.interactive can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin.command.client.search.interactive.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui uses atuin_ai.resume_tui.catchup, so a change to atuin_ai.resume_tui.catchup can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_ai.resume_tui.catchup.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui uses atuin_ai.resume_tui.source, so a change to atuin_ai.resume_tui.source can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_ai.resume_tui.source.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui uses atuin_ai.resume_tui.worker, so a change to atuin_ai.resume_tui.worker can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_ai.resume_tui.worker.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui uses atuin_ai.resume_tui.resumer, so a change to atuin_ai.resume_tui.resumer can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_ai.resume_tui.resumer.
Position
Below the diagonal: atuin_ai.resume_tui uses a module listed above it, which is the healthy direction.
22→23 atuin_ai.resume_tui uses atuin_ai.resume_tui.statepart of a loop✕
Connections
2 pairs of types, where a type in atuin_ai.resume_tui uses a type in atuin_ai.resume_tui.state.
atuin_ai.resume_tui uses atuin_ai.resume_tui.state, so a change to atuin_ai.resume_tui.state can break atuin_ai.resume_tui, while a change to atuin_ai.resume_tui can't break atuin_ai.resume_tui.state.
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.
atuin_ai.resume_tui.state uses atuin_ai.fsm.events, so a change to atuin_ai.fsm.events can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_ai.fsm.events.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin_client.settings, so a change to atuin_client.settings can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_client.settings.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin.command.client.search.interactive, so a change to atuin.command.client.search.interactive can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin.command.client.search.interactive.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin_ai.resume_tui.catchup, so a change to atuin_ai.resume_tui.catchup can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_ai.resume_tui.catchup.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin_ai.resume_tui.source, so a change to atuin_ai.resume_tui.source can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_ai.resume_tui.source.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin_ai.resume_tui.render, so a change to atuin_ai.resume_tui.render can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_ai.resume_tui.render.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin_ai.resume_tui.resumer, so a change to atuin_ai.resume_tui.resumer can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_ai.resume_tui.resumer.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.state uses atuin_ai.resume_tui, so a change to atuin_ai.resume_tui can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_ai.resume_tui.
Position
Below the diagonal: atuin_ai.resume_tui.state uses a module listed above it, which is the healthy direction.
23→24 atuin_ai.resume_tui.state uses atuin_common.io.line_readerpart of a loop✕
Connections
1 pair of types, where a type in atuin_ai.resume_tui.state uses a type in atuin_common.io.line_reader.
atuin_ai.resume_tui.state uses atuin_common.io.line_reader, so a change to atuin_common.io.line_reader can break atuin_ai.resume_tui.state, while a change to atuin_ai.resume_tui.state can't break atuin_common.io.line_reader.
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.
atuin_common.io.line_reader uses atuin_ai.resume_tui.state, so a change to atuin_ai.resume_tui.state can break atuin_common.io.line_reader, while a change to atuin_common.io.line_reader can't break atuin_ai.resume_tui.state.
Position
Below the diagonal: atuin_common.io.line_reader uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.markdown uses atuin_client.settings, so a change to atuin_client.settings can break atuin_ai.resume_tui.markdown, while a change to atuin_ai.resume_tui.markdown can't break atuin_client.settings.
Position
Below the diagonal: atuin_ai.resume_tui.markdown uses a module listed above it, which is the healthy direction.
atuin_ai.resume_tui.markdown uses atuin_common.io.line_reader, so a change to atuin_common.io.line_reader can break atuin_ai.resume_tui.markdown, while a change to atuin_ai.resume_tui.markdown can't break atuin_common.io.line_reader.
Position
Below the diagonal: atuin_ai.resume_tui.markdown uses a module listed above it, which is the healthy direction.
25→38 atuin_ai.resume_tui.markdown uses atuin.command.client.search.inspector.browserpart of a loop✕
Connections
3 pairs of types, where a type in atuin_ai.resume_tui.markdown uses a type in atuin.command.client.search.inspector.browser.
atuin_ai.resume_tui.markdown uses atuin.command.client.search.inspector.browser, so a change to atuin.command.client.search.inspector.browser can break atuin_ai.resume_tui.markdown, while a change to atuin_ai.resume_tui.markdown can't break atuin.command.client.search.inspector.browser.
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.
atuin_domain.record uses atuin_ai.resume_tui.markdown, so a change to atuin_ai.resume_tui.markdown can break atuin_domain.record, while a change to atuin_domain.record can't break atuin_ai.resume_tui.markdown.
Position
Below the diagonal: atuin_domain.record uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.database uses atuin_client.ai_session.database.query, so a change to atuin_client.ai_session.database.query can break atuin_client.ai_session.database, while a change to atuin_client.ai_session.database can't break atuin_client.ai_session.database.query.
Position
Below the diagonal: atuin_client.ai_session.database uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.database uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_client.ai_session.database, while a change to atuin_client.ai_session.database can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_client.ai_session.database uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.database uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_client.ai_session.database, while a change to atuin_client.ai_session.database can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_client.ai_session.database uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.database uses atuin_ai.resume_tui.source, so a change to atuin_ai.resume_tui.source can break atuin_client.ai_session.database, while a change to atuin_client.ai_session.database can't break atuin_ai.resume_tui.source.
Position
Below the diagonal: atuin_client.ai_session.database uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.database uses atuin_domain.record, so a change to atuin_domain.record can break atuin_client.ai_session.database, while a change to atuin_client.ai_session.database can't break atuin_domain.record.
Position
Below the diagonal: atuin_client.ai_session.database uses a module listed above it, which is the healthy direction.
27→31 atuin_client.ai_session.database uses atuin_client.databasepart of a loop✕
Connections
1 pair of types, where a type in atuin_client.ai_session.database uses a type in atuin_client.database.
atuin_client.ai_session.database uses atuin_client.database, so a change to atuin_client.database can break atuin_client.ai_session.database, while a change to atuin_client.ai_session.database can't break atuin_client.database.
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→33 atuin_client.ai_session.database uses atuin.logs.heldpart of a loop✕
Connections
1 pair of types, where a type in atuin_client.ai_session.database uses a type in atuin.logs.held.
atuin_client.ai_session.database uses atuin.logs.held, so a change to atuin.logs.held can break atuin_client.ai_session.database, while a change to atuin_client.ai_session.database can't break atuin.logs.held.
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.
atuin_client.record.sqlite_store uses atuin_client.ai_session.database.query, so a change to atuin_client.ai_session.database.query can break atuin_client.record.sqlite_store, while a change to atuin_client.record.sqlite_store can't break atuin_client.ai_session.database.query.
Position
Below the diagonal: atuin_client.record.sqlite_store uses a module listed above it, which is the healthy direction.
atuin_client.record.sqlite_store uses atuin_ai.resume_tui.markdown, so a change to atuin_ai.resume_tui.markdown can break atuin_client.record.sqlite_store, while a change to atuin_client.record.sqlite_store can't break atuin_ai.resume_tui.markdown.
Position
Below the diagonal: atuin_client.record.sqlite_store uses a module listed above it, which is the healthy direction.
atuin_client.record.sqlite_store uses atuin_domain.record, so a change to atuin_domain.record can break atuin_client.record.sqlite_store, while a change to atuin_client.record.sqlite_store can't break atuin_domain.record.
Position
Below the diagonal: atuin_client.record.sqlite_store uses a module listed above it, which is the healthy direction.
28→31 atuin_client.record.sqlite_store uses atuin_client.databasepart of a loop✕
Connections
1 pair of types, where a type in atuin_client.record.sqlite_store uses a type in atuin_client.database.
atuin_client.record.sqlite_store uses atuin_client.database, so a change to atuin_client.database can break atuin_client.record.sqlite_store, while a change to atuin_client.record.sqlite_store can't break atuin_client.database.
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.
atuin_client.ai_session.store uses atuin_ai.resume_tui.markdown, so a change to atuin_ai.resume_tui.markdown can break atuin_client.ai_session.store, while a change to atuin_client.ai_session.store can't break atuin_ai.resume_tui.markdown.
Position
Below the diagonal: atuin_client.ai_session.store uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.store uses atuin_domain.record, so a change to atuin_domain.record can break atuin_client.ai_session.store, while a change to atuin_client.ai_session.store can't break atuin_domain.record.
Position
Below the diagonal: atuin_client.ai_session.store uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.store uses atuin_client.ai_session.database, so a change to atuin_client.ai_session.database can break atuin_client.ai_session.store, while a change to atuin_client.ai_session.store can't break atuin_client.ai_session.database.
Position
Below the diagonal: atuin_client.ai_session.store uses a module listed above it, which is the healthy direction.
atuin_client.ai_session.store uses atuin_client.record.sqlite_store, so a change to atuin_client.record.sqlite_store can break atuin_client.ai_session.store, while a change to atuin_client.ai_session.store can't break atuin_client.record.sqlite_store.
Position
Below the diagonal: atuin_client.ai_session.store uses a module listed above it, which is the healthy direction.
29→33 atuin_client.ai_session.store uses atuin.logs.heldpart of a loop✕
Connections
1 pair of types, where a type in atuin_client.ai_session.store uses a type in atuin.logs.held.
atuin_client.ai_session.store uses atuin.logs.held, so a change to atuin.logs.held can break atuin_client.ai_session.store, while a change to atuin_client.ai_session.store can't break atuin.logs.held.
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.
atuin_client.history uses atuin_client.ai_session.database.query, so a change to atuin_client.ai_session.database.query can break atuin_client.history, while a change to atuin_client.history can't break atuin_client.ai_session.database.query.
Position
Below the diagonal: atuin_client.history uses a module listed above it, which is the healthy direction.
atuin_client.history uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_client.history, while a change to atuin_client.history can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_client.history uses a module listed above it, which is the healthy direction.
atuin_client.history uses atuin_client.ai_session.store, so a change to atuin_client.ai_session.store can break atuin_client.history, while a change to atuin_client.history can't break atuin_client.ai_session.store.
Position
Below the diagonal: atuin_client.history uses a module listed above it, which is the healthy direction.
atuin_client.database uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_client.database, while a change to atuin_client.database can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_client.database uses a module listed above it, which is the healthy direction.
atuin_client.database uses atuin_client.settings, so a change to atuin_client.settings can break atuin_client.database, while a change to atuin_client.database can't break atuin_client.settings.
Position
Below the diagonal: atuin_client.database uses a module listed above it, which is the healthy direction.
atuin_client.database uses atuin_common.harnesstools.continuation, so a change to atuin_common.harnesstools.continuation can break atuin_client.database, while a change to atuin_client.database can't break atuin_common.harnesstools.continuation.
Position
Below the diagonal: atuin_client.database uses a module listed above it, which is the healthy direction.
atuin_client.database uses atuin_client.history, so a change to atuin_client.history can break atuin_client.database, while a change to atuin_client.database can't break atuin_client.history.
Position
Below the diagonal: atuin_client.database uses a module listed above it, which is the healthy direction.
atuin_client.import uses atuin_common.harnesstools.continuation, so a change to atuin_common.harnesstools.continuation can break atuin_client.import, while a change to atuin_client.import can't break atuin_common.harnesstools.continuation.
Position
Below the diagonal: atuin_client.import uses a module listed above it, which is the healthy direction.
atuin_client.import uses atuin_client.history, so a change to atuin_client.history can break atuin_client.import, while a change to atuin_client.import can't break atuin_client.history.
Position
Below the diagonal: atuin_client.import uses a module listed above it, which is the healthy direction.
atuin.logs.held uses atuin_ai.fsm.events, so a change to atuin_ai.fsm.events can break atuin.logs.held, while a change to atuin.logs.held can't break atuin_ai.fsm.events.
Position
Below the diagonal: atuin.logs.held uses a module listed above it, which is the healthy direction.
atuin.logs.held uses atuin_client.database, so a change to atuin_client.database can break atuin.logs.held, while a change to atuin.logs.held can't break atuin_client.database.
Position
Below the diagonal: atuin.logs.held uses a module listed above it, which is the healthy direction.
atuin_daemon.client uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_daemon.client, while a change to atuin_daemon.client can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_daemon.client uses a module listed above it, which is the healthy direction.
atuin_daemon.client uses atuin_client.settings, so a change to atuin_client.settings can break atuin_daemon.client, while a change to atuin_daemon.client can't break atuin_client.settings.
Position
Below the diagonal: atuin_daemon.client uses a module listed above it, which is the healthy direction.
atuin_daemon.client uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_daemon.client, while a change to atuin_daemon.client can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_daemon.client uses a module listed above it, which is the healthy direction.
atuin_daemon.client uses atuin_ai.resume_tui.source, so a change to atuin_ai.resume_tui.source can break atuin_daemon.client, while a change to atuin_daemon.client can't break atuin_ai.resume_tui.source.
Position
Below the diagonal: atuin_daemon.client uses a module listed above it, which is the healthy direction.
atuin_daemon.client uses atuin_client.history, so a change to atuin_client.history can break atuin_daemon.client, while a change to atuin_daemon.client can't break atuin_client.history.
Position
Below the diagonal: atuin_daemon.client uses a module listed above it, which is the healthy direction.
atuin_daemon.client uses atuin_client.database, so a change to atuin_client.database can break atuin_daemon.client, while a change to atuin_daemon.client can't break atuin_client.database.
Position
Below the diagonal: atuin_daemon.client uses a module listed above it, which is the healthy direction.
atuin_ai.tools.session.read uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin_ai.tools.session.read, while a change to atuin_ai.tools.session.read can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin_ai.tools.session.read uses a module listed above it, which is the healthy direction.
atuin_ai.tools.session.read uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_ai.tools.session.read, while a change to atuin_ai.tools.session.read can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_ai.tools.session.read uses a module listed above it, which is the healthy direction.
atuin_ai.tools.session.read uses atuin_ai.tools, so a change to atuin_ai.tools can break atuin_ai.tools.session.read, while a change to atuin_ai.tools.session.read can't break atuin_ai.tools.
Position
Below the diagonal: atuin_ai.tools.session.read uses a module listed above it, which is the healthy direction.
atuin_ai.tools.session.read uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_ai.tools.session.read, while a change to atuin_ai.tools.session.read can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_ai.tools.session.read uses a module listed above it, which is the healthy direction.
atuin_ai.tools.session.read uses atuin.logs.held, so a change to atuin.logs.held can break atuin_ai.tools.session.read, while a change to atuin_ai.tools.session.read can't break atuin.logs.held.
Position
Below the diagonal: atuin_ai.tools.session.read uses a module listed above it, which is the healthy direction.
atuin_ai.tools.session.read uses atuin_daemon.client, so a change to atuin_daemon.client can break atuin_ai.tools.session.read, while a change to atuin_ai.tools.session.read can't break atuin_daemon.client.
Position
Below the diagonal: atuin_ai.tools.session.read uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session uses atuin_ai.fsm.events, so a change to atuin_ai.fsm.events can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin_ai.fsm.events.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session uses atuin_client.ai_session.database.query, so a change to atuin_client.ai_session.database.query can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin_client.ai_session.database.query.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session uses atuin.command.client.search.interactive, so a change to atuin.command.client.search.interactive can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin.command.client.search.interactive.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session uses atuin_ai.resume_tui.render, so a change to atuin_ai.resume_tui.render can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin_ai.resume_tui.render.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session uses atuin_ai.resume_tui.resumer, so a change to atuin_ai.resume_tui.resumer can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin_ai.resume_tui.resumer.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session uses atuin.logs.held, so a change to atuin.logs.held can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin.logs.held.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session uses a module listed above it, which is the healthy direction.
36→39 atuin_common.harnesstools.opencode.session uses atuin_common.harnesstools.opencode.session.v2part of a loop✕
Connections
7 pairs of types, where a type in atuin_common.harnesstools.opencode.session uses a type in atuin_common.harnesstools.opencode.session.v2.
atuin_common.harnesstools.opencode.session uses atuin_common.harnesstools.opencode.session.v2, so a change to atuin_common.harnesstools.opencode.session.v2 can break atuin_common.harnesstools.opencode.session, while a change to atuin_common.harnesstools.opencode.session can't break atuin_common.harnesstools.opencode.session.v2.
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.
atuin_daemon.session_capture uses atuin_common.sync.blocking_pool, so a change to atuin_common.sync.blocking_pool can break atuin_daemon.session_capture, while a change to atuin_daemon.session_capture can't break atuin_common.sync.blocking_pool.
Position
Below the diagonal: atuin_daemon.session_capture uses a module listed above it, which is the healthy direction.
atuin_daemon.session_capture uses atuin_client.ai_session.model, so a change to atuin_client.ai_session.model can break atuin_daemon.session_capture, while a change to atuin_daemon.session_capture can't break atuin_client.ai_session.model.
Position
Below the diagonal: atuin_daemon.session_capture uses a module listed above it, which is the healthy direction.
atuin_daemon.session_capture uses atuin_ai.resume_tui.source, so a change to atuin_ai.resume_tui.source can break atuin_daemon.session_capture, while a change to atuin_daemon.session_capture can't break atuin_ai.resume_tui.source.
Position
Below the diagonal: atuin_daemon.session_capture uses a module listed above it, which is the healthy direction.
atuin_daemon.session_capture uses atuin_client.ai_session.database, so a change to atuin_client.ai_session.database can break atuin_daemon.session_capture, while a change to atuin_daemon.session_capture can't break atuin_client.ai_session.database.
Position
Below the diagonal: atuin_daemon.session_capture uses a module listed above it, which is the healthy direction.
atuin_daemon.session_capture uses atuin_client.ai_session.store, so a change to atuin_client.ai_session.store can break atuin_daemon.session_capture, while a change to atuin_daemon.session_capture can't break atuin_client.ai_session.store.
Position
Below the diagonal: atuin_daemon.session_capture uses a module listed above it, which is the healthy direction.
atuin_daemon.session_capture uses atuin.logs.held, so a change to atuin.logs.held can break atuin_daemon.session_capture, while a change to atuin_daemon.session_capture can't break atuin.logs.held.
Position
Below the diagonal: atuin_daemon.session_capture uses a module listed above it, which is the healthy direction.
atuin.command.client.search.inspector.browser uses atuin_client.settings.kv, so a change to atuin_client.settings.kv can break atuin.command.client.search.inspector.browser, while a change to atuin.command.client.search.inspector.browser can't break atuin_client.settings.kv.
Position
Below the diagonal: atuin.command.client.search.inspector.browser uses a module listed above it, which is the healthy direction.
atuin.command.client.search.inspector.browser uses atuin_client.settings, so a change to atuin_client.settings can break atuin.command.client.search.inspector.browser, while a change to atuin.command.client.search.inspector.browser can't break atuin_client.settings.
Position
Below the diagonal: atuin.command.client.search.inspector.browser uses a module listed above it, which is the healthy direction.
atuin.command.client.search.inspector.browser uses atuin_common.io.line_reader, so a change to atuin_common.io.line_reader can break atuin.command.client.search.inspector.browser, while a change to atuin.command.client.search.inspector.browser can't break atuin_common.io.line_reader.
Position
Below the diagonal: atuin.command.client.search.inspector.browser uses a module listed above it, which is the healthy direction.
atuin.command.client.search.inspector.browser uses atuin_client.history, so a change to atuin_client.history can break atuin.command.client.search.inspector.browser, while a change to atuin.command.client.search.inspector.browser can't break atuin_client.history.
Position
Below the diagonal: atuin.command.client.search.inspector.browser uses a module listed above it, which is the healthy direction.
atuin.command.client.search.inspector.browser uses atuin_client.database, so a change to atuin_client.database can break atuin.command.client.search.inspector.browser, while a change to atuin.command.client.search.inspector.browser can't break atuin_client.database.
Position
Below the diagonal: atuin.command.client.search.inspector.browser uses a module listed above it, which is the healthy direction.
atuin.command.client.search.inspector.browser uses atuin_ai.tools.session.read, so a change to atuin_ai.tools.session.read can break atuin.command.client.search.inspector.browser, while a change to atuin.command.client.search.inspector.browser can't break atuin_ai.tools.session.read.
Position
Below the diagonal: atuin.command.client.search.inspector.browser uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session.v2 uses atuin_client.ai_session.database.query, so a change to atuin_client.ai_session.database.query can break atuin_common.harnesstools.opencode.session.v2, while a change to atuin_common.harnesstools.opencode.session.v2 can't break atuin_client.ai_session.database.query.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session.v2 uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session.v2 uses atuin_common.harnesstools.session.model, so a change to atuin_common.harnesstools.session.model can break atuin_common.harnesstools.opencode.session.v2, while a change to atuin_common.harnesstools.opencode.session.v2 can't break atuin_common.harnesstools.session.model.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session.v2 uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session.v2 uses atuin.command.client.search.interactive, so a change to atuin.command.client.search.interactive can break atuin_common.harnesstools.opencode.session.v2, while a change to atuin_common.harnesstools.opencode.session.v2 can't break atuin.command.client.search.interactive.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session.v2 uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session.v2 uses atuin_client.ai_session.store, so a change to atuin_client.ai_session.store can break atuin_common.harnesstools.opencode.session.v2, while a change to atuin_common.harnesstools.opencode.session.v2 can't break atuin_client.ai_session.store.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session.v2 uses a module listed above it, which is the healthy direction.
atuin_common.harnesstools.opencode.session.v2 uses atuin_common.harnesstools.opencode.session, so a change to atuin_common.harnesstools.opencode.session can break atuin_common.harnesstools.opencode.session.v2, while a change to atuin_common.harnesstools.opencode.session.v2 can't break atuin_common.harnesstools.opencode.session.
Position
Below the diagonal: atuin_common.harnesstools.opencode.session.v2 uses a module listed above it, which is the healthy direction.
atuin_common.futures.stream.chunked uses atuin_client.database, so a change to atuin_client.database can break atuin_common.futures.stream.chunked, while a change to atuin_common.futures.stream.chunked can't break atuin_client.database.
Position
Below the diagonal: atuin_common.futures.stream.chunked uses a module listed above it, which is the healthy direction.
atuin_common.futures.stream.chunked uses atuin_common.harnesstools.opencode.session.v2, so a change to atuin_common.harnesstools.opencode.session.v2 can break atuin_common.futures.stream.chunked, while a change to atuin_common.futures.stream.chunked can't break atuin_common.harnesstools.opencode.session.v2.
Position
Below the diagonal: atuin_common.futures.stream.chunked uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 47% · Weak · gated by X3, X4, X5 ·
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
67
High / Critical
A02:2025 — Security Misconfiguration
39
High / Critical
A07:2025 — Authentication Failures
24
High / Critical
A03:2025 — Software Supply Chain Failures
9
Medium
Roadmap
First, enable strict null checking in the base TypeScript configuration and resolve existing assertions by properly narrowing types or making properties required. Next, address swallowed exceptions and replace interpolated log messages with structured logging to improve observability. Finally, resolve the identified leaked secrets in the Rust source files and create the missing architectural decision record to complete the compliance baseline.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps.
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 — 93
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 — 471
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 — 106
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 12
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 76 of 76 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 76 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 613 of 670 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 321 test files), but it was not re-run: its build outgrew the 6 GB scratch ceiling (6.278 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 29 | org.opencontainers.image.url="https://atuin.sh" \ -------------------- ERROR: failed to solve: debian:bookworm-20261020-slim: failed to resolve source metadata for docker.io/library/debian:bookworm-20261020-slim: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/bookworm-20261020-slim": Forbidden; runtime evidence skipped.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Rust, lua is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Rust, lua is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 141 further occurrence(s) are not listed individually; the score already reflects all 181.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
51 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was State::execute_action at 81. A further 8 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Action::from_str at 62 — they are counted neither in the figure above nor in this dimension's score. 3 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/atuin/src/command/client/search/keybindings/actions.rs (Action::from_str at 62), crates/atuin/src/command/client.rs (Cmd::run_async at 33), crates/atuin-common/src/harnesstools/note.rs (atuin_common::harnesstools::note::tool_note at 21). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 23 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with State::execute_action (cyclomatic 81), atuin::command::client::search::interactive::history (cyclomatic 72), AgentFsm::handle (cyclomatic 62). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with atuin::command::client::search::interactive::history (cognitive 167), Picker::run (cognitive 67), SessionList::render (cognitive 65). — 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.5 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.1 / 10Stronggated by 59 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 24 FileTooLong finding(s) in God Classes — start with session.rs (5), REDACTED (5), database.rs (2). — One of this dimension's main actionable groups (24 warning-level).
Resolve the 13 MethodTooLong finding(s) in God Classes — start with render.rs (3), REDACTED (2), interactive.rs (2). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 8 FunctionTooLong finding(s) in God Classes — start with interactive.rs, mcp.rs, inline.rs. — One of this dimension's main actionable groups (8 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
80 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 28 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with keymap.rs (2), app.rs, store.rs. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 9 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with resumer.rs, read.rs, database.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 9 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with store.rs (2), REDACTED, render.rs. — One of this dimension's main actionable groups (9 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.9 / 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.
14 production modules (Cargo+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence.
Off the main sequence: atuin-domain · ×2
Off the main sequence: atuin-common
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
D9 · Test Distribution9.7 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
2983 test methods: 2823 unit, 102 integration, 0 BDD, 58 e2e. The Rust suite contributes 2983 `#[test]` function(s) across 321 file(s) declaring at least one; its unit/integration split is Cargo's own — 19 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
38 outdated, 0 yanked direct Cargo dependencies. 146 of 147 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: arboard · ×38
What to do
Improve Dependency Hygiene — currently 8.1/10. — 38 outdated, 0 yanked direct Cargo dependencies. 146 of 147 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.
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.
Resolve the 14 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (4), REDACTED (4). — One of this dimension's main actionable groups (14 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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 709 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, 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 a Python pyproject.toml/requirements.txt (pip/uv/Poetry), 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 31 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED (5), state.rs (2), interactive.rs. — One of this dimension's main actionable groups (31 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with info.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.9 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
43 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/atuin-client/src/ai_session/database.rs. Counted over 395 of the 535 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
87 deducted task-comment markers across 181450 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 84 TodoComment finding(s) in Explicit Debt — start with REDACTED (23), history_journal.rs (5), store.rs (5). — One of this dimension's main actionable groups (84 warning-level).
Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with settings.rs (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with doctor.rs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 57 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
5 of 15 build units (Cargo, Python) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
67 finding(s): 0 critical, 65 high, 2 medium, 0 low. 45 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 16 file(s) — `REDACTED` (lines 7–16), `crates/atuin-ai/src/resume_tui/tests.rs` (line 1218), `crates/atuin-client/src/ai_session/database.rs` (line 1122, line 1263, line 1271, …), `crates/atuin-client/src/ai_session/store.rs` (line 1393, line 1443), `crates/atuin-client/src/database.rs` (line 1565, line 1608, line 1626, …), … (+11 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (12 issue-level).
Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 45 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (46 issue-level, 1 of them charged here).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 29 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (26), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 5 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 395 of the 535 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with REDACTED, pull.rs, client.rs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with store.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
0/1 workload(s) run every container under a seccomp profile; 0/1 declare an AppArmor/SELinux profile.
No seccomp profileREDACTED:3
What to do
Resolve the 1 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 9 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
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.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps.
Enforce HTTPS on the server that receives this data: terminate TLS in it (axum-server/actix bind_rustls, tonic ServerTlsConfig, a tokio-rustls acceptor) and send Strict-Transport-Security, or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 13 of 14 project(s) that lack one — worth up to 1.9 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Only 9/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/atuin-domain`, `crates/atuin-pty-proxy`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Do you agree with this assessment?
P5 · DR & Backup7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×4) — crates/atuin-ai/src/stream.rs:150, crates/atuin-client/src/hub.rs:306, crates/atuin-client/src/hub.rs:349, …
What to do
Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Security — Read from this repository's Rust source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository serves HTTP itself (`Server::builder()` (crates/atuin-daemon/src/server.rs:49)), so its Rust source was also read for the server controls: TLS served or HSTS set, security response headers, cookie flags and inbound validation — each credited where its Rust spelling appears in production source, not proven on every route. A Rocket 0.5 application is credited the headers Rocket's default `Shield` sends unless it attaches its own, and its cookie jar's SameSite=Strict default; a session middleware its default cookie flags.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `Server::builder()` (crates/atuin-daemon/src/server.rs:49).
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `Server::builder()` (crates/atuin-daemon/src/server.rs:49).
What to do
Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen. Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — crates/atuin-common/res/harnesstools/pi/atuin.ts:59, crates/atuin-common/res/harnesstools/opencode/atuin.ts:131, crates/atuin-common/res/harnesstools/opencode/atuin.v2.ts:137
What to do
Swallowed exception (empty catch)
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.
`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/atuin-server/src/settings.rs:123
`error!` at line 43 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/atuin-server/src/handlers/user.rs:43
`debug!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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/atuin-server/src/handlers/user.rs:56
`error!` at line 60 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/atuin-server/src/handlers/user.rs:60
`error!` at line 103 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/atuin-server/src/handlers/user.rs:103
`debug!` at line 134 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/atuin-server/src/handlers/user.rs:134
`error!` at line 138 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/atuin-server/src/handlers/user.rs:138
`error!` at line 168 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/atuin-server/src/handlers/user.rs:168
`error!` at line 192 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/atuin-server/src/handlers/user.rs:192
`debug!` at line 202 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/atuin-server/src/handlers/user.rs:202
`error!` at line 206 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/atuin-server/src/handlers/user.rs:206
`error!` at line 42 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/atuin-server/src/handlers/v0/record.rs:42
`error!` at line 61 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/atuin-server/src/handlers/v0/record.rs:61
`error!` at line 94 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/atuin-server/src/handlers/v0/record.rs:94
`error!` at line 23 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/atuin-server/src/handlers/v0/store.rs:23
`debug!` at line 446 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/atuin-server/src/db/mod.rs:446
`debug!` at line 23 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`. (×2) — crates/atuin-scripts/src/database.rs:23, crates/atuin-kv/src/database.rs:23
`debug!` at line 111 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/atuin-scripts/src/database.rs:111
`debug!` at line 168 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/atuin-scripts/src/database.rs:168
`debug!` at line 182 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/atuin-scripts/src/database.rs:182
`debug!` at line 83 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/atuin-scripts/src/execution.rs:83
`debug!` at line 121 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/atuin-scripts/src/execution.rs:121
`debug!` at line 248 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/atuin-scripts/src/execution.rs:248
`debug!` at line 270 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/atuin-scripts/src/execution.rs:270
`warn!` at line 92 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/atuin-scripts/src/store.rs:92
`warn!` at line 100 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/atuin-scripts/src/store.rs:100
`debug!` at line 93 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/atuin-kv/src/database.rs:93
`debug!` at line 103 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/atuin-kv/src/database.rs:103
`warn!` at line 135 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/atuin-kv/src/store.rs:135
`warn!` at line 172 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/atuin-kv/src/store.rs:172
`warn!` at line 308 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/atuin-dotfiles/src/store.rs:308
`warn!` at line 326 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/atuin-dotfiles/src/store.rs:326
`warn!` at line 352 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/atuin-dotfiles/src/store/var.rs:352
`warn!` at line 370 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/atuin-dotfiles/src/store/var.rs:370
`warn!` at line 96 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/atuin-daemon/src/daemon.rs:96
`error!` 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: `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/atuin-daemon/src/history_journal.rs:434
`warn!` at line 453 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/atuin-daemon/src/history_journal.rs:453
`error!` at line 649 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/atuin-daemon/src/history_journal.rs:649
`error!` at line 57 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/atuin-daemon/src/server.rs:57
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
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 — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a struct, Diesel table, SeaORM entity or SQL migration table named for it — a SeaORM ActiveModelBehavior hook or database trigger that records each change, or an event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. A delete/anonymise identifier was seen but did not co-occur with GDPR vocabulary or a subject-id shape, so it was not credited (e.g. a save-slot DeleteAccount()). Implement erasure, data export/portability and consent tracking over the subject's records.
Not included — 46 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: 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 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).
AX4 Dependency direction — not applicable to a transaction-script/CRUD architecture (the inward-dependency rule is for layered/clean styles)
AX6 Interface segregation — no exported interface declares behaviour
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 — docker build failed (exit 1) — 29 | org.opencontainers.image.url="https://atuin.sh" \ -------------------- ERROR: failed to solve: debian:bookworm-20261020-slim: failed to resolve source metadata for docker.io/library/debian:bookworm-20261020-slim: failed to do request: Head "https://registry-1.docker.io/v2/library/debian/manifests/bookworm-20261020-slim": Forbidden; runtime evidence skipped 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.
D10 Test Quality — ~9205 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; Python, Rust, TypeScript not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .rs, .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
TodoComment crates/atuin-pty-proxy/src/foreground.rs:52— /// TODO(taylordotfish): Remove this once <https://github.com/bytecodealliance/rustix/issues/1678>
TodoComment crates/atuin-domain/src/record/mod.rs:33— /// TODO(ATU-589): Remove the field.
TodoComment crates/atuin-domain/src/record/mod.rs:99— // TODO(ellie): Optimize the storage here. We use a bunch of IDs, and currently store — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-domain/src/record/tag.rs:91— // TODO(markovejnovic): Figure out a better way to avoid the implicit `Clone` in here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-domain/src/record/tag.rs:105— // TODO(markovejnovic): Figure out a better way to avoid the implicit `Clone` in here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-domain/src/record/version.rs:43— // TODO(markovejnovic): Figure out a better way to avoid the implicit `Clone` in here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-domain/src/record/version.rs:57— // TODO(markovejnovic): Figure out a better way to avoid the implicit `Clone` in here. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-domain/src/caps/mod.rs:36— //! # TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/client.rs:169— // TODO(markovejnovic): A more flexible implementation would be to iterate into chunks that — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/history_journal.rs:209— /// TODO(markovejnovic): This probably shouldn't be injected in [`HistoryJournal`]. Perhaps a — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/history_journal.rs:443— // TODO(markovejnovic): This is a little bit hacked-together. I'm thinking it would be good — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/history_journal.rs:456— // TODO(#4052): This is inherently racy -- any add_history operations added between this
TodoComment crates/atuin-daemon/src/history_journal.rs:631— // TODO(#4052): This is inherently racy -- any add_history operations added between this
TodoComment crates/atuin-daemon/src/components/search.rs:123— // TODO(#4052): This is inherently racy -- any add_history operations added between this
TodoComment crates/atuin-daemon/src/components/search.rs:328— // TODO(#4052): This is inherently racy -- any add_history operations added between this
TodoComment crates/atuin-daemon/src/history_journal.rs:639— // TODO(markovejnovic): This is obviously incorrect behavior, keeping the previous — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/sync/engine/worker.rs:124— // TODO(markovejnovic): We should definitely not be creating new stores, but this is pending — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/sync/engine/worker.rs:208— // TODO(markovejnovic): The fact that we rebuild the SyncSession on every single iteration — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/sync/engine/worker.rs:274— // TODO(markovejnovic): Figure out what's happening with [`HistoryStore::incremental_build`] — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/service/mod.rs:99— /// TODO(markovejnovic): Do not use the global Settings but pass DaemonSettings. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/service/mod.rs:130— /// TODO(markovejnovic): Do not use the global Settings but pass DaemonSettings. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/service/mod.rs:176— /// TODO(markovejnovic): Do not use the global Settings but pass DaemonSettings. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/service/mod.rs:255— // TODO(markovejnovic): `self.connection` predates the lock. A client that replaced the — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/service/pidfile.rs:215— /// TODO(taylordotfish): On Windows, this locks the entire byte range of the pidfile, which — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/atuin-daemon/src/service/backend/subproc/unix.rs:29— // TODO(markovejnovic): We should have some sort of DirsProvider or something like that — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Hotspot: crates/atuin/src/command/client/search/interactive.rs crates/atuin/src/command/client/search/interactive.rs:497— crates/atuin/src/command/client/search/interactive.rs changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 81 in State::execute_action at line 497. 7 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin/src/command/client/search/interactive.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/atuin/src/command/client.rs crates/atuin/src/command/client.rs:292— crates/atuin/src/command/client.rs changed 32 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in Cmd::run_async at line 292. 7 of those changes were fix/bug commits, and the other 25 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin/src/command/client.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/atuin-client/src/database.rs crates/atuin-client/src/database.rs:714— crates/atuin-client/src/database.rs changed 34 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Sqlite::search at line 714. 8 of those changes were fix/bug commits, and the other 26 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-client/src/database.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/atuin-ai/src/resume_tui/mod.rs crates/atuin-ai/src/resume_tui/mod.rs:836— crates/atuin-ai/src/resume_tui/mod.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in Picker::run at line 836. 2 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/resume_tui/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/atuin-ai/src/resume_tui/state.rs crates/atuin-ai/src/resume_tui/state.rs:1030— crates/atuin-ai/src/resume_tui/state.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in State::execute_action at line 1030. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/resume_tui/state.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/atuin-ai/src/tui/app.rs crates/atuin-ai/src/tui/app.rs:323— crates/atuin-ai/src/tui/app.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in AiApp::handle_fsm at line 323. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/tui/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/atuin-daemon/src/session_capture/mod.rs crates/atuin-daemon/src/session_capture/mod.rs:225— crates/atuin-daemon/src/session_capture/mod.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in Sink::withhold_unsafe_output at line 225. 5 of those changes were fix/bug commits, and the other 20 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-daemon/src/session_capture/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/atuin-ai/src/tools/mod.rs crates/atuin-ai/src/tools/mod.rs:1116— crates/atuin-ai/src/tools/mod.rs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in AtuinHistoryToolCall::execute at line 1116. 4 of those changes were fix/bug commits, 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/tools/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/atuin-pty-proxy/src/runtime.rs crates/atuin-pty-proxy/src/runtime.rs:107— crates/atuin-pty-proxy/src/runtime.rs changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in atuin_pty_proxy::runtime::run at line 107. 6 of those changes were fix/bug commits, 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-pty-proxy/src/runtime.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: crates/atuin-ai/src/resume_tui/render.rs crates/atuin-ai/src/resume_tui/render.rs:485— crates/atuin-ai/src/resume_tui/render.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in SessionList::render at line 485. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/resume_tui/render.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/atuin/src/command/client/search.rs crates/atuin/src/command/client/search.rs:153— crates/atuin/src/command/client/search.rs changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in Cmd::run at line 153. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin/src/command/client/search.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/atuin-ai/src/commands/resume.rs crates/atuin-ai/src/commands/resume.rs:419— crates/atuin-ai/src/commands/resume.rs changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in atuin_ai::commands::resume::run at line 419. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/commands/resume.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/atuin-ai/src/fsm/mod.rs crates/atuin-ai/src/fsm/mod.rs:249— crates/atuin-ai/src/fsm/mod.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in AgentFsm::handle at line 249. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/fsm/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: REDACTED REDACTED:498— REDACTED changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in atuin_common::harnesstools::opencode::rehydrate::export_minting at line 498. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- REDACTED`: 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/atuin-common/src/harnesstools/codex/session.rs crates/atuin-common/src/harnesstools/codex/session.rs:1333— crates/atuin-common/src/harnesstools/codex/session.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in CodexMessage::content at line 1333. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-common/src/harnesstools/codex/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/atuin/src/command/client/search/keybindings/actions.rs crates/atuin/src/command/client/search/keybindings/actions.rs:86— crates/atuin/src/command/client/search/keybindings/actions.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 62 in Action::from_str at line 86. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin/src/command/client/search/keybindings/actions.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/atuin-client/src/ai_session/store.rs crates/atuin-client/src/ai_session/store.rs:580— crates/atuin-client/src/ai_session/store.rs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AiSessionStore::reproject_series at line 580. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-client/src/ai_session/store.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/atuin-ai/src/mcp.rs crates/atuin-ai/src/mcp.rs:102— crates/atuin-ai/src/mcp.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in AtuinMcp::call_tool at line 102. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/mcp.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/atuin-ai/src/tools/session/read.rs crates/atuin-ai/src/tools/session/read.rs:380— crates/atuin-ai/src/tools/session/read.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in AtuinThreadsReadToolCall::render at line 380. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/tools/session/read.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/atuin-common/src/harnesstools/continuation.rs crates/atuin-common/src/harnesstools/continuation.rs:622— crates/atuin-common/src/harnesstools/continuation.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in atuin_common::harnesstools::continuation::turns at line 622. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-common/src/harnesstools/continuation.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/atuin-client/src/meta.rs crates/atuin-client/src/meta.rs:282— crates/atuin-client/src/meta.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in MetaStore::migrate_files at line 282. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-client/src/meta.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/atuin-ai/src/stream.rs crates/atuin-ai/src/stream.rs:93— crates/atuin-ai/src/stream.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in atuin_ai::stream::create_chat_stream at line 93. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/stream.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/atuin-ai/src/resume_tui/resumer.rs crates/atuin-ai/src/resume_tui/resumer.rs:669— crates/atuin-ai/src/resume_tui/resumer.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in HarnessResumer::catch_up at line 669. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/resume_tui/resumer.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/atuin-ai/src/resume_tui/worker.rs crates/atuin-ai/src/resume_tui/worker.rs:290— crates/atuin-ai/src/resume_tui/worker.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in atuin_ai::resume_tui::worker::details at line 290. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-ai/src/resume_tui/worker.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/atuin-client/src/ai_session/database/write.rs crates/atuin-client/src/ai_session/database/write.rs:263— crates/atuin-client/src/ai_session/database/write.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in AiSessionDatabase::append_in at line 263. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin-client/src/ai_session/database/write.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: search/interactive.rs crates/atuin/src/command/client/search/interactive.rs— FileTooLong — 1622 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 1122 over it, 3.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: resume_tui/render.rs crates/atuin-ai/src/resume_tui/render.rs— FileTooLong — 1548 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 1048 over it, 3.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: opencode/session.rs crates/atuin-common/src/harnesstools/opencode/session.rs— FileTooLong — 1442 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 942 over it, 2.88× 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: ai_session/database.rs crates/atuin-client/src/ai_session/database.rs— FileTooLong — 1253 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 69% of them inside a single declaration: AiSessionDatabase (2 blocks, 182-1742). The bar is 500 significant lines; this is 753 over it, 2.51× 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/settings.rs crates/atuin-client/src/settings.rs— FileTooLong — 1217 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 717 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: codex/session.rs crates/atuin-common/src/harnesstools/codex/session.rs— FileTooLong — 909 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 409 over it, 1.82× 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/session.rs crates/atuin-ai/src/commands/session.rs— FileTooLong — 907 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 407 over it, 1.81× 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: client/history.rs crates/atuin/src/command/client/history.rs— FileTooLong — 884 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 384 over it, 1.77× 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/database.rs crates/atuin-client/src/database.rs— FileTooLong — 871 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: Sqlite (3 blocks, 284-1134). The bar is 500 significant lines; this is 371 over it, 1.74× 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: tui/app.rs crates/atuin-ai/src/tui/app.rs— FileTooLong — 848 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 92% of them inside a single declaration: AiApp (3 blocks, 101-1280). The bar is 500 significant lines; this is 348 over it, 1.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: database/write.rs crates/atuin-client/src/ai_session/database/write.rs— FileTooLong — 813 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 83% of them inside a single declaration: AiSessionDatabase (219-1189). The bar is 500 significant lines; this is 313 over it, 1.63× 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: resume_tui/markdown.rs crates/atuin-ai/src/resume_tui/markdown.rs— FileTooLong — 798 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 298 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: session/v2.rs crates/atuin-common/src/harnesstools/opencode/session/v2.rs— FileTooLong — 765 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 265 over it, 1.53× 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: tools/mod.rs crates/atuin-ai/src/tools/mod.rs— FileTooLong — 749 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 249 over it, 1.50× 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: fsm/mod.rs crates/atuin-ai/src/fsm/mod.rs— FileTooLong — 720 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 89% of them inside a single declaration: AgentFsm (2 blocks, 183-1239). The bar is 500 significant lines; this is 220 over it, 1.44× 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: resume_tui/state.rs crates/atuin-ai/src/resume_tui/state.rs— FileTooLong — 707 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 82% of them inside a single declaration: State (2 blocks, 235-1153). The bar is 500 significant lines; this is 207 over it, 1.41× 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: ccode/session.rs crates/atuin-common/src/harnesstools/ccode/session.rs— FileTooLong — 702 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 202 over it, 1.40× 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: resume_tui/mod.rs crates/atuin-ai/src/resume_tui/mod.rs— FileTooLong — 691 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 32 free functions. The bar is 500 significant lines; this is 191 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: resume_tui/resumer.rs crates/atuin-ai/src/resume_tui/resumer.rs— FileTooLong — 686 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 186 over it, 1.37× 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: REDACTED REDACTED— FileTooLong — 686 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 34 free functions. The bar is 500 significant lines; this is 186 over it, 1.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: session_capture/mod.rs crates/atuin-daemon/src/session_capture/mod.rs— FileTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 122 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: session/read.rs crates/atuin-ai/src/tools/session/read.rs— FileTooLong — 544 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 44 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: pi/session.rs crates/atuin-common/src/harnesstools/pi/session.rs— FileTooLong — 543 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 43 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: view/mod.rs crates/atuin-ai/src/tui/view/mod.rs— FileTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 38 free functions. The bar is 500 significant lines; this is 41 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
atuin_ai::stream::create_chat_stream (cognitive 50) crates/atuin-ai/src/stream.rs:93— atuin_ai::stream::create_chat_stream has cognitive complexity 50 (threshold 15). Drivers by points: if/else 20 (40 pts), match/switch 4 (7 pts), boolean chains 2, loops 1 (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.
atuin_ai::resume_tui::markdown::wrap (cognitive 42) crates/atuin-ai/src/resume_tui/markdown.rs:1074— atuin_ai::resume_tui::markdown::wrap has cognitive complexity 42 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 4 (6 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_ai::tui::state::events_to_messages (cognitive 34) crates/atuin-ai/src/tui/state.rs:86— atuin_ai::tui::state::events_to_messages has cognitive complexity 34 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 3 (8 pts), match/switch 2 (5 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_ai::commands::resume::run (cognitive 31) crates/atuin-ai/src/commands/resume.rs:419— atuin_ai::commands::resume::run has cognitive complexity 31 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 4, match/switch 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_ai::resume_tui::render::list_lines (cognitive 28) crates/atuin-ai/src/resume_tui/render.rs:363— atuin_ai::resume_tui::render::list_lines has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 3 (4 pts), boolean chains 3 (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.
atuin_ai::tools::session::read::render_message (cognitive 28) crates/atuin-ai/src/tools/session/read.rs:552— atuin_ai::tools::session::read::render_message has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 2 (5 pts), match/switch 1 (2 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.
atuin_ai::commands::session::tail (cognitive 27) crates/atuin-ai/src/commands/session.rs:383— atuin_ai::commands::session::tail has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (20 pts), match/switch 2 (5 pts), boolean chains 1, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_ai::commands::session::import (cognitive 23) crates/atuin-ai/src/commands/session.rs:495— atuin_ai::commands::session::import has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 4 (10 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.
atuin_ai::resume_tui::worker::details (cognitive 23) crates/atuin-ai/src/resume_tui/worker.rs:290— atuin_ai::resume_tui::worker::details has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 3 (7 pts), loops 3 (5 pts) (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.
atuin_ai::tui::bridge::stream_bridge (cognitive 23) crates/atuin-ai/src/tui/bridge.rs:23— atuin_ai::tui::bridge::stream_bridge has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 3 (8 pts), 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.
atuin_ai::commands::inline::run_inline_tui (cognitive 22) crates/atuin-ai/src/commands/inline.rs:195— atuin_ai::commands::inline::run_inline_tui has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 3, match/switch 2 (3 pts), 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.
atuin_ai::resume_tui::title::clean (cognitive 22) crates/atuin-ai/src/resume_tui/title.rs:297— atuin_ai::resume_tui::title::clean has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 4 (7 pts), 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.
atuin_ai::resume_tui::query::parse (cognitive 20) crates/atuin-ai/src/resume_tui/query.rs:107— atuin_ai::resume_tui::query::parse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (7 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_ai::permissions::shell::scope_matches_words (cognitive 19) crates/atuin-ai/src/permissions/shell.rs:394— atuin_ai::permissions::shell::scope_matches_words has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_ai::resume_tui::title::kind (cognitive 18) crates/atuin-ai/src/resume_tui/title.rs:163— atuin_ai::resume_tui::title::kind has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, loops 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_ai::resume_tui::worker::transcripts (cognitive 18) crates/atuin-ai/src/resume_tui/worker.rs:145— atuin_ai::resume_tui::worker::transcripts has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 2 (5 pts), loops 2 (3 pts) (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.
atuin_ai::tui::persist::spawn_persist_worker (cognitive 18) crates/atuin-ai/src/tui/persist.rs:39— atuin_ai::tui::persist::spawn_persist_worker has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_ai::commands::session::write_message_text (cognitive 17) crates/atuin-ai/src/commands/session.rs:728— atuin_ai::commands::session::write_message_text has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), 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.
atuin_ai::tools::execute_shell_command_streaming (cognitive 16) crates/atuin-ai/src/tools/mod.rs:855— atuin_ai::tools::execute_shell_command_streaming has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (8 pts), if/else 4 (6 pts), boolean chains 1, loops 1 (nesting depth added 5). 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.
atuin_ai::tools::session::elsewhere_note (cognitive 16) crates/atuin-ai/src/tools/session/mod.rs:106— atuin_ai::tools::session::elsewhere_note has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
atuin_common::harnesstools::continuation::turns (cognitive 50) crates/atuin-common/src/harnesstools/continuation.rs:622— atuin_common::harnesstools::continuation::turns has cognitive complexity 50 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 5 (16 pts), loops 5 (8 pts), boolean chains 6 (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.
atuin_common::harnesstools::opencode::rehydrate::export_minting (cognitive 48) REDACTED:498— atuin_common::harnesstools::opencode::rehydrate::export_minting has cognitive complexity 48 (threshold 15). Drivers by points: if/else 20 (37 pts), loops 5, boolean chains 4, match/switch 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::harnesstools::opencode::rehydrate::v2::export (cognitive 40) crates/atuin-common/src/harnesstools/opencode/rehydrate/v2.rs:150— atuin_common::harnesstools::opencode::rehydrate::v2::export has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (20 pts), match/switch 5 (12 pts), boolean chains 4, loops 3 (4 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.
atuin_common::harnesstools::session::patch::parse_files (cognitive 33) crates/atuin-common/src/harnesstools/session/patch.rs:271— atuin_common::harnesstools::session::patch::parse_files has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 2 (7 pts), boolean chains 2, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::harnesstools::codex::rehydrate::turns (cognitive 32) crates/atuin-common/src/harnesstools/codex/rehydrate.rs:425— atuin_common::harnesstools::codex::rehydrate::turns has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 5 (8 pts), boolean chains 4 (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.
atuin_common::harnesstools::rehydrate::join_notes (cognitive 31) crates/atuin-common/src/harnesstools/rehydrate.rs:266— atuin_common::harnesstools::rehydrate::join_notes has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (22 pts), match/switch 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::harnesstools::access::script::tokens (cognitive 29) crates/atuin-common/src/harnesstools/access/script.rs:90— atuin_common::harnesstools::access::script::tokens has cognitive complexity 29 (threshold 15). Drivers by points: loops 5 (13 pts), if/else 8 (9 pts), boolean chains 7 (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.
atuin_common::harnesstools::rehydrate::break_line_cycles (cognitive 25) crates/atuin-common/src/harnesstools/rehydrate.rs:370— atuin_common::harnesstools::rehydrate::break_line_cycles has cognitive complexity 25 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 5 (10 pts), match/switch 1 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::harnesstools::codex::hook_trust::atuin_hooks (cognitive 20) crates/atuin-common/src/harnesstools/codex/hook_trust.rs:96— atuin_common::harnesstools::codex::hook_trust::atuin_hooks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::secrets::redact_once (cognitive 19) REDACTED:643— atuin_common::secrets::redact_once has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::harnesstools::access::redirected (cognitive 18) crates/atuin-common/src/harnesstools/access.rs:154— atuin_common::harnesstools::access::redirected has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::harnesstools::note::render (cognitive 18) crates/atuin-common/src/harnesstools/note.rs:23— atuin_common::harnesstools::note::render has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::harnesstools::continuation::continue_at (cognitive 17) crates/atuin-common/src/harnesstools/continuation.rs:299— atuin_common::harnesstools::continuation::continue_at has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 3 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_common::harnesstools::opencode::rehydrate::v2::add (cognitive 17) crates/atuin-common/src/harnesstools/opencode/rehydrate/v2.rs:294— atuin_common::harnesstools::opencode::rehydrate::v2::add has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 4, boolean chains 2, loops 1 (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.
atuin_common::harnesstools::sync::ccode::liveness (cognitive 16) crates/atuin-common/src/harnesstools/sync/ccode.rs:123— atuin_common::harnesstools::sync::ccode::liveness has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), match/switch 2 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (6 lines × 2) crates/atuin-ai/src/resume_tui/keymap.rs:273— crates/atuin-ai/src/resume_tui/keymap.rs:273-278 | crates/atuin/src/command/client/search/keybindings/defaults.rs:289-294 — 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/atuin-ai/src/tui/app.rs:469— crates/atuin-ai/src/tui/app.rs:469-474 | crates/atuin-ai/src/tui/app.rs:737-742 — 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/atuin-dotfiles/src/store.rs:207— crates/atuin-dotfiles/src/store.rs:207-212 | crates/atuin-dotfiles/src/store/var.rs:256-261 — before extracting anything, compare `crates/atuin-dotfiles/src/store.rs` and `crates/atuin-dotfiles/src/store/var.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 80 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/atuin-dotfiles/src/store/var.rs:118— crates/atuin-dotfiles/src/store/var.rs:118-128 | crates/atuin-dotfiles/src/store/var.rs:155-160 — 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/atuin/src/command/client/search/keybindings/defaults.rs:111— crates/atuin/src/command/client/search/keybindings/defaults.rs:111-116 | crates/atuin/src/command/client/search/keybindings/defaults.rs:244-249 — 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/atuin-ai/src/resume_tui/keymap.rs:53— crates/atuin-ai/src/resume_tui/keymap.rs:53-58 | crates/atuin/src/command/client/search/keybindings/keymap.rs:95-100 — 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/atuin-client/src/database.rs:374— crates/atuin-client/src/database.rs:374-379 | crates/atuin-client/src/record/sqlite_store.rs:110-116 — 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/atuin-ai/src/tools/mod.rs:426— crates/atuin-ai/src/tools/mod.rs:426-433 | crates/atuin-ai/src/tools/mod.rs:624-629 — 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/atuin-client/src/record/sqlite_store.rs:434— crates/atuin-client/src/record/sqlite_store.rs:434-440 | crates/atuin-client/src/record/sqlite_store.rs:454-459 — 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/atuin-common/src/db/sqlite/fts.rs:88— crates/atuin-common/src/db/sqlite/fts.rs:88-93 | crates/atuin-common/src/db/sqlite/fts.rs:106-111 — 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/atuin-ai/src/commands/inline.rs:481— crates/atuin-ai/src/commands/inline.rs:481-486 | crates/atuin-ai/src/models.rs:62-67 — 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/atuin-client/src/api_client.rs:165— crates/atuin-client/src/api_client.rs:165-170 | crates/atuin-client/src/api_client.rs:188-193 — 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/atuin-client/src/import/xonsh.rs:54— crates/atuin-client/src/import/xonsh.rs:54-59 | crates/atuin-client/src/import/xonsh_sqlite.rs:75-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) crates/atuin-common/src/harnesstools/sync/codex.rs:89— crates/atuin-common/src/harnesstools/sync/codex.rs:89-94 | crates/atuin-common/src/harnesstools/sync/codex.rs:107-112 — 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.
MethodTooLong: AgentFsm.handle crates/atuin-ai/src/fsm/mod.rs:249— MethodTooLong — handle runs 304 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 204 over it, 3.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.
MethodTooLong: State.execute_action crates/atuin/src/command/client/search/interactive.rs:497— MethodTooLong — execute_action runs 267 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 167 over it, 2.67× 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: State.draw_main crates/atuin-ai/src/resume_tui/render.rs:1263— MethodTooLong — draw_main runs 243 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 143 over it, 2.43× 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: State.draw_inner crates/atuin/src/command/client/search/interactive.rs:951— MethodTooLong — draw_inner runs 220 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 120 over it, 2.20× 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: AiSessionDatabase.append_in crates/atuin-client/src/ai_session/database/write.rs:263— MethodTooLong — append_in runs 212 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 112 over it, 2.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: SessionList.render crates/atuin-ai/src/resume_tui/render.rs:485— MethodTooLong — render runs 155 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 55 over it, 1.55× 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: Picker.run crates/atuin-ai/src/resume_tui/mod.rs:836— MethodTooLong — run 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: AiApp.handle_fsm crates/atuin-ai/src/tui/app.rs:323— MethodTooLong — handle_fsm runs 135 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 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WrappedStats.new crates/atuin/src/command/client/wrapped.rs:26— MethodTooLong — new runs 123 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 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: State.draw_inspect crates/atuin-ai/src/resume_tui/render.rs:1887— MethodTooLong — draw_inspect runs 110 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 10 over it, 1.10× 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: AiApp.execute_tool crates/atuin-ai/src/tui/app.rs:598— MethodTooLong — execute_tool runs 108 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 8 over it, 1.08× 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: Sqlite.search crates/atuin-client/src/database.rs:714— MethodTooLong — search runs 107 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 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.
MethodTooLong: Settings.builder_with_data_dir crates/atuin-client/src/settings.rs:1579— MethodTooLong — builder_with_data_dir runs 102 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Cmd::run (cognitive 33) crates/atuin/src/command/client/search.rs:153— Cmd::run has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (20 pts), loops 2 (7 pts), boolean chains 5, match/switch 1 (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.
Cmd::run (cognitive 24) crates/atuin/src/command/client/import.rs:60— Cmd::run has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (23 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Cmd::run (cognitive 22) crates/atuin/src/command/client/account/register.rs:29— Cmd::run has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 3 (6 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cmd::run_hub_login (cognitive 20) crates/atuin/src/command/client/account/login.rs:90— Cmd::run_hub_login has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 1 (3 pts), boolean chains 2, loops 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.
Cmd::handle_run (cognitive 20) crates/atuin/src/command/client/scripts.rs:289— Cmd::handle_run has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Cmd::run (cognitive 18) crates/atuin/src/command/client/kv.rs:61— Cmd::run has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Cmd::handle_get (cognitive 18) crates/atuin/src/command/client/scripts.rs:389— Cmd::handle_get has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), loops 3 (8 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.
Cmd::handle_edit (cognitive 18) crates/atuin/src/command/client/scripts.rs:442— Cmd::handle_edit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (18 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.
Cmd::prompt_and_store_key (cognitive 17) crates/atuin/src/command/client/account/login.rs:210— Cmd::prompt_and_store_key has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), match/switch 3 (7 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (11 lines × 2) crates/atuin-ai/src/resume_tui/resumer.rs:744— crates/atuin-ai/src/resume_tui/resumer.rs:744-754 | crates/atuin-ai/src/resume_tui/resumer.rs:821-831 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) crates/atuin-ai/src/tools/session/read.rs:267— crates/atuin-ai/src/tools/session/read.rs:267-277 | crates/atuin-client/src/ai_session/database.rs:1430-1440 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) crates/atuin-client/src/database.rs:619— crates/atuin-client/src/database.rs:619-629 | crates/atuin-client/src/database.rs:732-742 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) crates/atuin-client/src/record/sqlite_store.rs:353— crates/atuin-client/src/record/sqlite_store.rs:353-363 | crates/atuin-client/src/record/sqlite_store.rs:458-468 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) crates/atuin-common/src/harnesstools/ccode/session.rs:181— crates/atuin-common/src/harnesstools/ccode/session.rs:181-191 | crates/atuin-common/src/harnesstools/codex/session.rs:211-221 — `crates/atuin-common/src/harnesstools/ccode/session.rs` and `crates/atuin-common/src/harnesstools/codex/session.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 4 separate duplicated blocks between them, totalling at least 38 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 (11 lines × 2) crates/atuin/src/command/client/history.rs:1052— crates/atuin/src/command/client/history.rs:1052-1062 | crates/atuin/src/command/client/history.rs:1104-1114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) crates/atuin-ai/src/fsm/mod.rs:822— crates/atuin-ai/src/fsm/mod.rs:822-832 | crates/atuin-ai/src/fsm/mod.rs:845-858 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) crates/atuin-dotfiles/src/store.rs:94— crates/atuin-dotfiles/src/store.rs:94-104 | crates/atuin-dotfiles/src/store/var.rs:72-82 — before extracting anything, compare `crates/atuin-dotfiles/src/store.rs` and `crates/atuin-dotfiles/src/store/var.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 80 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 (11 lines × 2) crates/atuin-client/src/import/nu.rs:27— crates/atuin-client/src/import/nu.rs:27-37 | crates/atuin-client/src/import/nu_histdb.rs:89-99 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) crates/atuin-ai/src/resume_tui/mod.rs:663— crates/atuin-ai/src/resume_tui/mod.rs:663-671 | crates/atuin-ai/src/resume_tui/mod.rs:787-795 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/atuin-ai/src/resume_tui/render.rs:992— crates/atuin-ai/src/resume_tui/render.rs:992-1000 | crates/atuin-ai/src/resume_tui/render.rs:1508-1516 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/atuin-ai/src/resume_tui/resumer.rs:764— crates/atuin-ai/src/resume_tui/resumer.rs:764-772 | crates/atuin-ai/src/resume_tui/resumer.rs:838-846 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:176— crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:176-184 | crates/atuin-common/src/harnesstools/pi/rehydrate.rs:179-187 — `crates/atuin-common/src/harnesstools/ccode/rehydrate.rs` and `crates/atuin-common/src/harnesstools/pi/rehydrate.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 5 separate duplicated blocks between them, totalling at least 54 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 (9 lines × 2) crates/atuin-common/src/harnesstools/ccode/session.rs:89— crates/atuin-common/src/harnesstools/ccode/session.rs:89-97 | crates/atuin-common/src/harnesstools/codex/session.rs:102-110 — `crates/atuin-common/src/harnesstools/ccode/session.rs` and `crates/atuin-common/src/harnesstools/codex/session.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 4 separate duplicated blocks between them, totalling at least 38 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 (9 lines × 2) crates/atuin-dotfiles/src/store.rs:290— crates/atuin-dotfiles/src/store.rs:290-298 | crates/atuin-dotfiles/src/store/var.rs:334-342 — before extracting anything, compare `crates/atuin-dotfiles/src/store.rs` and `crates/atuin-dotfiles/src/store/var.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 80 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 (9 lines × 2) crates/atuin/src/command/client/sync.rs:108— crates/atuin/src/command/client/sync.rs:108-116 | crates/atuin/src/command/client/sync.rs:136-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) crates/atuin-dotfiles/src/store.rs:175— crates/atuin-dotfiles/src/store.rs:175-183 | crates/atuin-dotfiles/src/store/var.rs:223-231 — before extracting anything, compare `crates/atuin-dotfiles/src/store.rs` and `crates/atuin-dotfiles/src/store/var.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 80 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 (9 lines × 2) crates/atuin-common/src/harnesstools/opencode/session/v2.rs:732— crates/atuin-common/src/harnesstools/opencode/session/v2.rs:732-740 | crates/atuin-common/src/harnesstools/opencode/session/v2.rs:750-758 — 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.
atuin_ai::stream::create_chat_stream (cyclomatic 30) crates/atuin-ai/src/stream.rs:93— atuin_ai::stream::create_chat_stream has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
atuin_ai::commands::resume::run (cyclomatic 22) crates/atuin-ai/src/commands/resume.rs:419— atuin_ai::commands::resume::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.
atuin_ai::resume_tui::markdown::wrap (cyclomatic 22) crates/atuin-ai/src/resume_tui/markdown.rs:1074— atuin_ai::resume_tui::markdown::wrap 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.
atuin_ai::resume_tui::worker::details (cyclomatic 20) crates/atuin-ai/src/resume_tui/worker.rs:290— atuin_ai::resume_tui::worker::details 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.
atuin_ai::tools::session::read::render_message (cyclomatic 19) crates/atuin-ai/src/tools/session/read.rs:552— atuin_ai::tools::session::read::render_message 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.
atuin_ai::resume_tui::title::clean (cyclomatic 18) crates/atuin-ai/src/resume_tui/title.rs:297— atuin_ai::resume_tui::title::clean has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
atuin_ai::tui::state::events_to_messages (cyclomatic 17) crates/atuin-ai/src/tui/state.rs:86— atuin_ai::tui::state::events_to_messages 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.
atuin_ai::resume_tui::render::list_lines (cyclomatic 16) crates/atuin-ai/src/resume_tui/render.rs:363— atuin_ai::resume_tui::render::list_lines 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.
State::draw_inner (cognitive 60) crates/atuin/src/command/client/search/interactive.rs:951— State::draw_inner has cognitive complexity 60 (threshold 15). Drivers by points: if/else 34 (49 pts), match/switch 5 (6 pts), boolean chains 5 (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.
State::execute_action (cognitive 53) crates/atuin/src/command/client/search/interactive.rs:497— State::execute_action has cognitive complexity 53 (threshold 15). Drivers by points: if/else 26 (44 pts), match/switch 3 (5 pts), loops 2 (4 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.
State::draw_main (cognitive 53) crates/atuin-ai/src/resume_tui/render.rs:1263— State::draw_main has cognitive complexity 53 (threshold 15). Drivers by points: if/else 29 (34 pts), boolean chains 13, loops 2 (3 pts), match/switch 3 (nesting depth added 6). 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.
State::build_help (cognitive 35) crates/atuin-ai/src/resume_tui/render.rs:1606— State::build_help has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (26 pts), match/switch 2 (5 pts), boolean chains 2, loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
State::handle_key_input (cognitive 22) crates/atuin/src/command/client/search/interactive.rs:371— State::handle_key_input has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (17 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 6). 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.
State::settle_chooser (cognitive 19) crates/atuin-ai/src/resume_tui/chooser.rs:243— State::settle_chooser has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
State::build_preview (cognitive 16) crates/atuin/src/command/client/search/interactive.rs:1446— State::build_preview has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (5 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
State::build_input (cognitive 16) crates/atuin-ai/src/resume_tui/render.rs:1734— State::build_input has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), match/switch 3 (5 pts), boolean chains 1, loops 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FunctionTooLong: atuin::command::client::search::interactive::history crates/atuin/src/command/client/search/interactive.rs:1810— FunctionTooLong — atuin::command::client::search::interactive::history runs 315 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 215 over it, 3.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: atuin_ai::mcp::tool_definitions crates/atuin-ai/src/mcp.rs:199— FunctionTooLong — atuin_ai::mcp::tool_definitions runs 140 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 40 over it, 1.40× 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: atuin_ai::commands::inline::run_inline_tui crates/atuin-ai/src/commands/inline.rs:195— FunctionTooLong — atuin_ai::commands::inline::run_inline_tui runs 125 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 25 over it, 1.25× 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: atuin_scripts::execution::execute_script_interactive crates/atuin-scripts/src/execution.rs:75— FunctionTooLong — atuin_scripts::execution::execute_script_interactive runs 117 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: atuin_pty_proxy::runtime::run crates/atuin-pty-proxy/src/runtime.rs:107— FunctionTooLong — atuin_pty_proxy::runtime::run 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: atuin_common::harnesstools::opencode::rehydrate::export_minting REDACTED:498— FunctionTooLong — atuin_common::harnesstools::opencode::rehydrate::export_minting runs 110 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 10 over it, 1.10× 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: atuin_daemon::boot crates/atuin-daemon/src/lib.rs:59— FunctionTooLong — atuin_daemon::boot 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.
FunctionTooLong: atuin_ai::tui::state::events_to_messages crates/atuin-ai/src/tui/state.rs:86— FunctionTooLong — atuin_ai::tui::state::events_to_messages runs 102 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: State crates/atuin/src/command/client/search/interactive.rs:159— ClassTooLong — 952 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 29 methods, 2 blocks, lines 159-1492. The bar is 400 significant lines; this is 552 over it, 2.38× 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: AiSessionDatabase crates/atuin-client/src/ai_session/database.rs:182— ClassTooLong — 868 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 92 methods, 2 blocks, lines 182-1742. The bar is 400 significant lines; this is 468 over it, 2.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AiApp crates/atuin-ai/src/tui/app.rs:101— ClassTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 25 methods, 3 blocks, lines 101-1280. The bar is 400 significant lines; this is 377 over it, 1.94× 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: AgentFsm crates/atuin-ai/src/fsm/mod.rs:183— ClassTooLong — 641 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 2 blocks, lines 183-1239. The bar is 400 significant lines; this is 241 over it, 1.60× 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: Settings crates/atuin-client/src/settings.rs:1035— ClassTooLong — 610 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 43 methods, 3 blocks, lines 1035-1997. The bar is 400 significant lines; this is 210 over it, 1.53× 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: State crates/atuin-ai/src/resume_tui/state.rs:235— ClassTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 81 methods, 2 blocks, lines 235-1153. The bar is 400 significant lines; this is 178 over it, 1.45× 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: Sqlite crates/atuin-client/src/database.rs:284— ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 27 methods, 3 blocks, lines 284-1134. The bar is 400 significant lines; this is 119 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Renderer crates/atuin-ai/src/resume_tui/markdown.rs:357— ClassTooLong — 417 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 16 methods, 2 blocks, lines 357-937. The bar is 400 significant lines; this is 17 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.
Duplicated block (7 lines × 2) crates/atuin-scripts/src/execution.rs:185— crates/atuin-scripts/src/execution.rs:185-191 | crates/atuin-scripts/src/execution.rs:213-219 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/atuin/src/command/client/account/login.rs:52— crates/atuin/src/command/client/account/login.rs:52-58 | crates/atuin/src/command/client/account/register.rs:30-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/atuin/src/command/client/history.rs:586— crates/atuin/src/command/client/history.rs:586-592 | crates/atuin/src/command/client/history.rs:1163-1169 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/atuin-client/src/import/nu_histdb.rs:66— crates/atuin-client/src/import/nu_histdb.rs:66-72 | crates/atuin-client/src/import/zsh_histdb.rs:76-82 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) crates/atuin-common/src/harnesstools/access.rs:144— crates/atuin-common/src/harnesstools/access.rs:144-150 | crates/atuin-common/src/harnesstools/continuation/tools.rs:56-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/atuin-dotfiles/src/store.rs:70— crates/atuin-dotfiles/src/store.rs:70-77 | crates/atuin-kv/src/store/record.rs:46-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) crates/atuin-client/src/ai_session/database/write.rs:153— crates/atuin-client/src/ai_session/database/write.rs:153-159 | crates/atuin-client/src/ai_session/database/write.rs:167-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:188— crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:188-194 | crates/atuin-common/src/harnesstools/pi/rehydrate.rs:194-200 — `crates/atuin-common/src/harnesstools/ccode/rehydrate.rs` and `crates/atuin-common/src/harnesstools/pi/rehydrate.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 5 separate duplicated blocks between them, totalling at least 54 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.
State::execute_action (cyclomatic 81) crates/atuin/src/command/client/search/interactive.rs:497— State::execute_action has cyclomatic complexity 81 (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.
State::execute_action (cyclomatic 59) crates/atuin-ai/src/resume_tui/state.rs:1030— State::execute_action has cyclomatic complexity 59 (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.
State::draw_main (cyclomatic 41) crates/atuin-ai/src/resume_tui/render.rs:1263— State::draw_main has cyclomatic complexity 41 (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.
State::draw_inner (cyclomatic 32) crates/atuin/src/command/client/search/interactive.rs:951— State::draw_inner has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
State::build_help (cyclomatic 21) crates/atuin-ai/src/resume_tui/render.rs:1606— State::build_help has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
State::settle_chooser (cyclomatic 16) crates/atuin-ai/src/resume_tui/chooser.rs:243— State::settle_chooser 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.
State::chooser_key (cyclomatic 16) crates/atuin-ai/src/resume_tui/chooser.rs:379— State::chooser_key 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.
atuin_common::harnesstools::continuation::turns (cyclomatic 32) crates/atuin-common/src/harnesstools/continuation.rs:622— atuin_common::harnesstools::continuation::turns has cyclomatic complexity 32 (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.
atuin_common::harnesstools::opencode::rehydrate::export_minting (cyclomatic 29) REDACTED:498— atuin_common::harnesstools::opencode::rehydrate::export_minting 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.
atuin_common::harnesstools::opencode::rehydrate::v2::export (cyclomatic 24) crates/atuin-common/src/harnesstools/opencode/rehydrate/v2.rs:150— atuin_common::harnesstools::opencode::rehydrate::v2::export 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.
atuin_common::harnesstools::access::script::tokens (cyclomatic 20) crates/atuin-common/src/harnesstools/access/script.rs:90— atuin_common::harnesstools::access::script::tokens has cyclomatic complexity 20 (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.
atuin_common::harnesstools::session::patch::parse_files (cyclomatic 19) crates/atuin-common/src/harnesstools/session/patch.rs:271— atuin_common::harnesstools::session::patch::parse_files 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.
atuin_common::harnesstools::codex::rehydrate::turns (cyclomatic 18) crates/atuin-common/src/harnesstools/codex/rehydrate.rs:425— atuin_common::harnesstools::codex::rehydrate::turns 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.
atuin_common::harnesstools::rehydrate::join_notes (cyclomatic 17) crates/atuin-common/src/harnesstools/rehydrate.rs:266— atuin_common::harnesstools::rehydrate::join_notes 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.
atuin::command::client::search::interactive::history (cognitive 167) crates/atuin/src/command/client/search/interactive.rs:1810— atuin::command::client::search::interactive::history has cognitive complexity 167 (threshold 15). Drivers by points: if/else 56 (134 pts), boolean chains 11, loops 4 (11 pts), match/switch 5 (11 pts) (nesting depth added 91). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin::command::client::search::engines::db::get_highlight_indices_fulltext (cognitive 24) crates/atuin/src/command/client/search/engines/db.rs:50— atuin::command::client::search::engines::db::get_highlight_indices_fulltext has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (8 pts), match/switch 1 (2 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.
atuin::command::client::config::set_deep_key (cognitive 17) crates/atuin/src/command/client/config.rs:677— atuin::command::client::config::set_deep_key has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin::command::client::history::print_list (cognitive 17) crates/atuin/src/command/client/history.rs:195— atuin::command::client::history::print_list has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 3 (4 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AiApp::handle_fsm (cognitive 50) crates/atuin-ai/src/tui/app.rs:323— AiApp::handle_fsm has cognitive complexity 50 (threshold 15). Drivers by points: if/else 14 (34 pts), match/switch 5 (14 pts), boolean chains 1, loops 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AiApp::update (cognitive 28) crates/atuin-ai/src/tui/app.rs:998— AiApp::update has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (19 pts), match/switch 4 (7 pts), boolean chains 2 (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.
AiApp::execute_tool (cognitive 27) crates/atuin-ai/src/tui/app.rs:598— AiApp::execute_tool has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 5, match/switch 3 (5 pts) (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.
AiApp::keymap (cognitive 16) crates/atuin-ai/src/tui/app.rs:1217— AiApp::keymap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
Renderer::table_lines (cognitive 40) crates/atuin-ai/src/resume_tui/markdown.rs:801— Renderer::table_lines has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (27 pts), loops 4 (6 pts), boolean chains 4, 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.
Renderer::text (cognitive 17) crates/atuin-ai/src/resume_tui/markdown.rs:646— Renderer::text has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Renderer::emit_block (cognitive 17) crates/atuin-ai/src/resume_tui/markdown.rs:731— Renderer::emit_block has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 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.
Renderer::end (cognitive 16) crates/atuin-ai/src/resume_tui/markdown.rs:554— Renderer::end has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Change coupling: REDACTED ↔ REDACTED crates/atuin-server/src/db/postgres/mod.rs:1— `crates/atuin-server/src/db/postgres/mod.rs` and `crates/atuin-server/src/db/sqlite/mod.rs` change together 93% of the time (13 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `bbcc20d0` refactor(server): share SQLite + Postgres Database impls via a blanke…; `5a6a4f23` refactor(server): polymorphic database (#4014); `3bcd94fe` fix(sqlite): prevent stale prepared-statement panic across migrations… (at that commit the files were still `crates/atuin-server-postgres/src/lib.rs` and `crates/atuin-server-sqlite/src/lib.rs`) — run `git show` on any of them.
Change coupling: pull.rs ↔ push.rs crates/atuin/src/command/client/store/pull.rs:1— `crates/atuin/src/command/client/store/pull.rs` and `crates/atuin/src/command/client/store/push.rs` change together 69% of the time (11 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `853584af` refactor(client): rename SyncEngine to SyncSession (#4130); `824c8716` perf(sync): parallel record downloads (#3955); `c06067b5` bug: avoid rare race condition in sync (#3972) — run `git show` on any of them.
Change coupling: client.rs ↔ server.rs crates/atuin-daemon/src/client.rs:1— `crates/atuin-daemon/src/client.rs` and `crates/atuin-daemon/src/server.rs` change together 57% of the time (8 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `1114043e` refactor(daemon): move daemon startup into the service module (atuins…; `10b11415` fix(daemon): verify daemon version in HTTP headers (atuinsh/atuin#4431); `2a6868ab` feat(daemon): change default daemon socket path (#3910) — run `git show` on any of them.
Change coupling: search.rs ↔ db.rs crates/atuin/src/command/client/search.rs:1— `crates/atuin/src/command/client/search.rs` and `crates/atuin/src/command/client/search/engines/db.rs` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — 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 `8c1ccccd` chore: add `OrFilter` as a replacement for `Vec`s as filter lists (#3…; `4147f845` fix(search): add `DbSearchMode`; correctly fall back to "fuzzy" in no…; `6ba6a892` feat(search): filter by shell in interactive search (#3692) — run `git show` on any of them.
Duplicated block (8 lines × 2) crates/atuin-ai/src/commands/resume.rs:698— crates/atuin-ai/src/commands/resume.rs:698-705 | crates/atuin-ai/src/commands/resume.rs:729-736 — 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/atuin/src/command/client/search/history_list.rs:391— crates/atuin/src/command/client/search/history_list.rs:391-398 | crates/atuin/src/command/client/search/history_list.rs:402-409 — 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/atuin-kv/src/store/record.rs:43— crates/atuin-kv/src/store/record.rs:43-50 | crates/atuin-kv/src/store/record.rs:66-73 — 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/atuin-daemon/src/output_capture/persistence/mod.rs:192— crates/atuin-daemon/src/output_capture/persistence/mod.rs:192-199 | crates/atuin-daemon/src/output_capture/persistence/mod.rs:202-209 — 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/atuin-ai/src/tui/app.rs:624— crates/atuin-ai/src/tui/app.rs:624-628 | crates/atuin-ai/src/tui/app.rs:663-667 — 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/atuin-daemon/src/service/backend/launchd/macos.rs:257— crates/atuin-daemon/src/service/backend/launchd/macos.rs:257-261 | crates/atuin-daemon/src/service/systemd/linux.rs:77-81 — 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/atuin-common/src/harnesstools/ccode/rehydrate.rs:148— crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:148-152 | crates/atuin-common/src/harnesstools/pi/rehydrate.rs:114-118 — `crates/atuin-common/src/harnesstools/ccode/rehydrate.rs` and `crates/atuin-common/src/harnesstools/pi/rehydrate.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 5 separate duplicated blocks between them, totalling at least 54 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 (5 lines × 2) crates/atuin-domain/src/record/tag.rs:103— crates/atuin-domain/src/record/tag.rs:103-107 | crates/atuin-domain/src/record/version.rs:55-59 — 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.
Outbound HTTP without resilience crates/atuin-ai/src/stream.rs:150— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/atuin-client/src/hub.rs:306— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/atuin-client/src/hub.rs:349— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience crates/atuin-client/src/hub.rs:368— `reqwest::Client::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
AiApp::handle_fsm (cyclomatic 37) crates/atuin-ai/src/tui/app.rs:323— AiApp::handle_fsm has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AiApp::update (cyclomatic 35) crates/atuin-ai/src/tui/app.rs:998— AiApp::update has cyclomatic complexity 35 (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.
AiApp::execute_tool (cyclomatic 22) crates/atuin-ai/src/tui/app.rs:598— AiApp::execute_tool 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.
AiSessionDatabase::append_in (cognitive 32) crates/atuin-client/src/ai_session/database/write.rs:263— AiSessionDatabase::append_in has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (19 pts), match/switch 5 (6 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 6). 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.
AiSessionDatabase::search (cognitive 20) crates/atuin-client/src/ai_session/database.rs:1117— AiSessionDatabase::search has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 3 (4 pts), match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AiSessionDatabase::attribute_call (cognitive 18) crates/atuin-client/src/ai_session/database/write.rs:956— AiSessionDatabase::attribute_call has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (6 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TooManyMethods: AiSessionDatabase crates/atuin-client/src/ai_session/database.rs:182— TooManyMethods — 92 methods, declared across 4 files: ai_session/database.rs (62), database/write.rs (19), database/watermark.rs (10), database/heads.rs (1). The bar is 30 methods; this is 62 over it, 3.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.
TooManyMethods: State crates/atuin-ai/src/resume_tui/state.rs:235— TooManyMethods — 81 methods, declared across 5 files: resume_tui/state.rs (42), resume_tui/render.rs (22), resume_tui/chooser.rs (11), resume_tui/panel.rs (4), +1 more file(s). The bar is 30 methods; this is 51 over it, 2.70× 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: Settings crates/atuin-client/src/settings.rs:1035— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFields: Settings crates/atuin-client/src/settings.rs:1035— TooManyFields — 70 stored fields beside 43 methods. The bar is 30 stored fields; this is 40 over it, 2.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: ReshEntry crates/atuin-client/src/import/resh.rs:20— TooManyFields — 51 stored fields. The bar is 30 stored fields; this is 21 over it, 1.70× 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: State crates/atuin-ai/src/resume_tui/state.rs:235— TooManyFields — 49 stored fields beside 81 methods. The bar is 30 stored fields; this is 19 over it, 1.63× 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.
Swallowed exception (empty catch) crates/atuin-common/res/harnesstools/pi/atuin.ts:59— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) crates/atuin-common/res/harnesstools/opencode/atuin.ts:131— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) crates/atuin-common/res/harnesstools/opencode/atuin.v2.ts:137— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Cmd::run (cyclomatic 23) crates/atuin/src/command/client/import.rs:60— Cmd::run has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Cmd::run (cyclomatic 22) crates/atuin/src/command/client/search.rs:153— Cmd::run 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.
Renderer::table_lines (cyclomatic 21) crates/atuin-ai/src/resume_tui/markdown.rs:801— Renderer::table_lines has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Renderer::end (cyclomatic 19) crates/atuin-ai/src/resume_tui/markdown.rs:554— Renderer::end 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.
FixmeComment crates/atuin-client/src/settings.rs:189— // FIXME: Can use upstream Dialect enum if https://github.com/stevedonovan/chrono-english/pull/16 is merged
FixmeComment crates/atuin-client/src/settings.rs:190— // FIXME: Above PR was merged, but dependency was changed to interim (fork of chrono-english) in the ... interim — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
SessionList::render (cognitive 65) crates/atuin-ai/src/resume_tui/render.rs:485— SessionList::render has cognitive complexity 65 (threshold 15). Drivers by points: if/else 27 (44 pts), boolean chains 12, match/switch 4 (8 pts), loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SessionList::render_row (cognitive 25) crates/atuin-ai/src/resume_tui/render.rs:798— SessionList::render_row has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_daemon::session_capture::engine::capture (cognitive 33) crates/atuin-daemon/src/session_capture/engine/mod.rs:153— atuin_daemon::session_capture::engine::capture has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (24 pts), match/switch 2 (5 pts), loops 2 (4 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_daemon::session_capture::tools::shape (cognitive 31) crates/atuin-daemon/src/session_capture/tools.rs:160— atuin_daemon::session_capture::tools::shape has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 3 (9 pts), match/switch 2 (3 pts), boolean chains 1 (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.
Sink::withhold_unsafe_output (cognitive 26) crates/atuin-daemon/src/session_capture/mod.rs:225— Sink::withhold_unsafe_output has cognitive complexity 26 (threshold 15). Drivers by points: match/switch 5 (12 pts), if/else 3 (7 pts), loops 3 (4 pts), boolean chains 3 (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.
Sink::append_locked (cognitive 17) crates/atuin-daemon/src/session_capture/mod.rs:369— Sink::append_locked has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (6 pts), match/switch 3 (6 pts), if/else 4, 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.
Tree::push (cognitive 25) crates/atuin-common/src/harnesstools/sync/ccode.rs:302— Tree::push has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 7, match/switch 4 (7 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Tree::newest_below (cognitive 18) crates/atuin-common/src/harnesstools/sync/ccode.rs:390— Tree::newest_below has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TreeWatcherPoller::observe_event (cognitive 22) crates/atuin-common/src/fs/tree_watcher/poller.rs:138— TreeWatcherPoller::observe_event has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (8 pts), match/switch 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.
TreeWatcherPoller::run (cognitive 20) crates/atuin-common/src/fs/tree_watcher/poller.rs:36— TreeWatcherPoller::run has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (10 pts), loops 2 (5 pts), match/switch 2 (5 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.
Duplicated block (23 lines × 2) crates/atuin-dotfiles/src/store.rs:227— crates/atuin-dotfiles/src/store.rs:227-249 | crates/atuin-dotfiles/src/store.rs:261-283 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2) crates/atuin-dotfiles/src/store/var.rs:274— crates/atuin-dotfiles/src/store/var.rs:274-296 | crates/atuin-dotfiles/src/store/var.rs:305-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) crates/atuin-client/src/import/replxx.rs:24— crates/atuin-client/src/import/replxx.rs:24-39 | crates/atuin-client/src/import/zsh.rs:35-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) crates/atuin-client/src/auth.rs:214— crates/atuin-client/src/auth.rs:214-229 | crates/atuin-client/src/auth.rs:245-260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) crates/atuin/src/command/client/account/link.rs:25— crates/atuin/src/command/client/account/link.rs:25-38 | crates/atuin/src/command/client/account/login.rs:188-201 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) crates/atuin/src/command/client/history.rs:1037— crates/atuin/src/command/client/history.rs:1037-1050 | crates/atuin/src/command/client/history.rs:1089-1102 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) crates/atuin-client/src/record/sync/mod.rs:345— crates/atuin-client/src/record/sync/mod.rs:345-356 | crates/atuin-client/src/record/sync/mod.rs:493-504 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) crates/atuin-client/src/auth.rs:386— crates/atuin-client/src/auth.rs:386-397 | crates/atuin-client/src/auth.rs:452-463 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) crates/atuin-dotfiles/src/store.rs:42— crates/atuin-dotfiles/src/store.rs:42-51 | crates/atuin-dotfiles/src/store/var.rs:36-45 — before extracting anything, compare `crates/atuin-dotfiles/src/store.rs` and `crates/atuin-dotfiles/src/store/var.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) crates/atuin-common/src/harnesstools/ccode/session.rs:74— crates/atuin-common/src/harnesstools/ccode/session.rs:74-83 | crates/atuin-common/src/harnesstools/codex/session.rs:81-90 — `crates/atuin-common/src/harnesstools/ccode/session.rs` and `crates/atuin-common/src/harnesstools/codex/session.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 4 separate duplicated blocks between them, totalling at least 38 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–7 lines × 2) crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:85— crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:85-91 | crates/atuin-common/src/harnesstools/pi/rehydrate.rs:84-89 — `crates/atuin-common/src/harnesstools/ccode/rehydrate.rs` and `crates/atuin-common/src/harnesstools/pi/rehydrate.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 5 separate duplicated blocks between them, totalling at least 54 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–7 lines × 2) crates/atuin-common/src/harnesstools/sync/ccode.rs:500— crates/atuin-common/src/harnesstools/sync/ccode.rs:500-506 | crates/atuin-common/src/harnesstools/sync/ccode.rs:598-603 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) crates/atuin-dotfiles/src/shell/bash.rs:22— crates/atuin-dotfiles/src/shell/bash.rs:22-34 | crates/atuin-dotfiles/src/shell/fish.rs:23-35 — before extracting anything, compare `crates/atuin-dotfiles/src/shell/bash.rs` and `crates/atuin-dotfiles/src/shell/fish.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 (13 lines × 2) crates/atuin-dotfiles/src/store.rs:300— crates/atuin-dotfiles/src/store.rs:300-312 | crates/atuin-dotfiles/src/store/var.rs:344-356 — before extracting anything, compare `crates/atuin-dotfiles/src/store.rs` and `crates/atuin-dotfiles/src/store/var.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 80 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.
Off the main sequence: atuin-domain — atuin-domain: abstractness 0.07, instability 0.10, distance 0.83 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
Off the main sequence: atuin-client — atuin-client: abstractness 0.06, instability 0.18, distance 0.76 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
atuin::command::client::search::interactive::history (cyclomatic 72) crates/atuin/src/command/client/search/interactive.rs:1810— atuin::command::client::search::interactive::history has cyclomatic complexity 72 (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.
AgentFsm::handle (cyclomatic 62) crates/atuin-ai/src/fsm/mod.rs:249— AgentFsm::handle has cyclomatic complexity 62 (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.
Picker::run (cyclomatic 45) crates/atuin-ai/src/resume_tui/mod.rs:836— Picker::run has cyclomatic complexity 45 (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.
SingleKey::parse (cyclomatic 45) crates/atuin-client/src/tui/key.rs:116— SingleKey::parse has cyclomatic complexity 45 (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.
SessionList::render (cyclomatic 43) crates/atuin-ai/src/resume_tui/render.rs:485— SessionList::render has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Sqlite::search (cyclomatic 28) crates/atuin-client/src/database.rs:714— Sqlite::search has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AtuinThreadsReadToolCall::render (cyclomatic 26) crates/atuin-ai/src/tools/session/read.rs:380— AtuinThreadsReadToolCall::render 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.
AiSessionDatabase::append_in (cyclomatic 26) crates/atuin-client/src/ai_session/database/write.rs:263— AiSessionDatabase::append_in has cyclomatic complexity 26 (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.
CodexMessage::content (cyclomatic 22) crates/atuin-common/src/harnesstools/codex/session.rs:1333— CodexMessage::content 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.
atuin_scripts::execution::execute_script_interactive (cyclomatic 22) crates/atuin-scripts/src/execution.rs:75— atuin_scripts::execution::execute_script_interactive 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.
MetaStore::migrate_files (cyclomatic 20) crates/atuin-client/src/meta.rs:282— MetaStore::migrate_files 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.
Canonical::render (cyclomatic 20) crates/atuin-common/src/harnesstools/continuation/tools.rs:167— Canonical::render 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.
Tree::push (cyclomatic 20) crates/atuin-common/src/harnesstools/sync/ccode.rs:302— Tree::push has cyclomatic complexity 20 (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.
atuin_pty_proxy::runtime::run (cyclomatic 20) crates/atuin-pty-proxy/src/runtime.rs:107— atuin_pty_proxy::runtime::run 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.
HarnessResumer::catch_up (cyclomatic 19) crates/atuin-ai/src/resume_tui/resumer.rs:669— HarnessResumer::catch_up 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.
OpencodeListener::watch (cyclomatic 19) crates/atuin-common/src/harnesstools/opencode/session.rs:366— OpencodeListener::watch 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.
Sink::withhold_unsafe_output (cyclomatic 19) crates/atuin-daemon/src/session_capture/mod.rs:225— Sink::withhold_unsafe_output 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.
AtuinHistoryToolCall::execute (cyclomatic 18) crates/atuin-ai/src/tools/mod.rs:1116— AtuinHistoryToolCall::execute has cyclomatic complexity 18 (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.
Analysis::find_heads (cyclomatic 17) crates/atuin-client/src/ai_session/database/heads.rs:155— Analysis::find_heads 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.
AiSessionStore::reproject_series (cyclomatic 16) crates/atuin-client/src/ai_session/store.rs:580— AiSessionStore::reproject_series 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.
CcodeMessage::content (cyclomatic 16) crates/atuin-common/src/harnesstools/ccode/session.rs:984— CcodeMessage::content 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.
atuin.v2.setup (cyclomatic 16) crates/atuin-common/res/harnesstools/opencode/atuin.v2.ts:161— atuin.v2.setup has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 166, 200, 190). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Repeated repair: crates/atuin/src/command/client/info.rs crates/atuin/src/command/client/info.rs:5— crates/atuin/src/command/client/info.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is atuin::command::client::info::run at line 5), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(client): resolve relative config paths beside config.toml, not the cwd (atuinsh/atuin#4479)”; “fix(config): avoid shadowing data dir, fix gaps in avoidance logic (atuinsh/atuin#4421)”; “fix(config): don't let a default ~/.atuin/config.toml hide the legacy config, and warn when one does (atuinsh/atuin#4420)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 01:03:44 +00:00' --until='2026-10-26 01:03:44 +00:00' --full-history --no-merges -- crates/atuin/src/command/client/info.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.
HackComment crates/atuin/src/command/client/doctor.rs:33— // HACK ALERT! — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
Picker::run (cognitive 67) crates/atuin-ai/src/resume_tui/mod.rs:836— Picker::run has cognitive complexity 67 (threshold 15). Drivers by points: if/else 24 (51 pts), match/switch 3 (8 pts), boolean chains 7, loops 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgentFsm::handle (cognitive 60) crates/atuin-ai/src/fsm/mod.rs:249— AgentFsm::handle has cognitive complexity 60 (threshold 15). Drivers by points: if/else 23 (50 pts), match/switch 3 (5 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpencodeListener::watch (cognitive 42) crates/atuin-common/src/harnesstools/opencode/session.rs:366— OpencodeListener::watch has cognitive complexity 42 (threshold 15). Drivers by points: match/switch 8 (22 pts), if/else 6 (19 pts), loops 1 (nesting depth added 27). 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.
AtuinThreadsReadToolCall::render (cognitive 38) crates/atuin-ai/src/tools/session/read.rs:380— AtuinThreadsReadToolCall::render has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (33 pts), boolean chains 3, loops 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_scripts::execution::execute_script_interactive (cognitive 35) crates/atuin-scripts/src/execution.rs:75— atuin_scripts::execution::execute_script_interactive has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (23 pts), loops 4 (6 pts), match/switch 4 (6 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.
Sqlite::search (cognitive 34) crates/atuin-client/src/database.rs:714— Sqlite::search has cognitive complexity 34 (threshold 15). Drivers by points: if/else 16 (25 pts), match/switch 4 (6 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetaStore::migrate_files (cognitive 33) crates/atuin-client/src/meta.rs:282— MetaStore::migrate_files has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (28 pts), boolean chains 5 (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.
atuin_pty_proxy::runtime::run (cognitive 32) crates/atuin-pty-proxy/src/runtime.rs:107— atuin_pty_proxy::runtime::run has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (18 pts), match/switch 5 (9 pts), loops 3, boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AiSessionStore::reproject_series (cognitive 29) crates/atuin-client/src/ai_session/store.rs:580— AiSessionStore::reproject_series has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 3 (6 pts), loops 2 (3 pts), boolean chains 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.
OpencodeSession::messages_from (cognitive 29) crates/atuin-common/src/harnesstools/opencode/session.rs:1646— OpencodeSession::messages_from has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 4 (10 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Pass::next (cognitive 27) crates/atuin-common/src/harnesstools/opencode/session/v2.rs:278— Pass::next has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (19 pts), match/switch 2 (6 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AtuinHistoryToolCall::execute (cognitive 24) crates/atuin-ai/src/tools/mod.rs:1116— AtuinHistoryToolCall::execute has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (18 pts), match/switch 3 (4 pts), boolean chains 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, 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.
atuin_client::ai_session::database::heads::break_cycles (cognitive 24) crates/atuin-client/src/ai_session/database/heads.rs:486— atuin_client::ai_session::database::heads::break_cycles has cognitive complexity 24 (threshold 15). Drivers by points: if/else 2 (10 pts), loops 4 (9 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Listener::events (cognitive 24) crates/atuin-common/src/harnesstools/session/mod.rs:200— Listener::events has cognitive complexity 24 (threshold 15). Drivers by points: match/switch 4 (13 pts), if/else 3 (9 pts), boolean chains 1, loops 1 (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Strategy::run (cognitive 23) REDACTED:48— Strategy::run has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 3 (6 pts), match/switch 2 (5 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.
OpencodeSessions::existing (cognitive 22) crates/atuin-common/src/harnesstools/opencode/session.rs:249— OpencodeSessions::existing has cognitive complexity 22 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (8 pts), match/switch 3 (5 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.
HarnessResumer::catch_up (cognitive 21) crates/atuin-ai/src/resume_tui/resumer.rs:669— HarnessResumer::catch_up has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (9 pts), match/switch 6 (7 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Analysis::find_heads (cognitive 21) crates/atuin-client/src/ai_session/database/heads.rs:155— Analysis::find_heads has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 8, match/switch 2 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryTokenizer::next (cognitive 20) crates/atuin-client/src/database.rs:1291— QueryTokenizer::next has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15 (20 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Pieces::next (cognitive 20) crates/atuin-common/src/string/highlighted.rs:290— Pieces::next has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
nextest-bktec.write_results (cognitive 20) .buildkite/scripts/nextest-bktec.py:71— nextest-bktec.write_results has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, loops 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.
SingleKey::parse (cognitive 19) crates/atuin-client/src/tui/key.rs:116— SingleKey::parse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 2 (3 pts), boolean chains 2, 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.
CodexMessage::content (cognitive 18) crates/atuin-common/src/harnesstools/codex/session.rs:1333— CodexMessage::content has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), match/switch 2 (3 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.
Output::rows (cognitive 17) crates/atuin/src/command/client/search/inspector/output.rs:169— Output::rows has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (9 pts), if/else 3 (7 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CcodeMessage::content (cognitive 17) crates/atuin-common/src/harnesstools/ccode/session.rs:984— CcodeMessage::content has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, match/switch 5 (8 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Stamper::track_calls (cognitive 17) crates/atuin-common/src/harnesstools/codex/session.rs:425— Stamper::track_calls has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin_history::stats::strip_leading_env_vars (cognitive 17) crates/atuin-history/src/stats.rs:120— atuin_history::stats::strip_leading_env_vars has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
atuin.v2.setup (cognitive 17) crates/atuin-common/res/harnesstools/opencode/atuin.v2.ts:161— atuin.v2.setup has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 4, loops 1, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 17 points belong to 3 function literals inside it that branch (lines 166, 200, 190). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AtuinThreadsSearchToolCall::run (cognitive 16) crates/atuin-ai/src/tools/session/search.rs:67— AtuinThreadsSearchToolCall::run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), match/switch 2, boolean chains 1, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Rows::write_step (cognitive 16) crates/atuin-common/src/harnesstools/continuation.rs:447— Rows::write_step has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (5 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×1
REDACTED
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Change coupling clique: store.rs, store.rs, store.rs crates/atuin-dotfiles/src/store.rs— 3 files — `crates/atuin-dotfiles/src/store.rs`, `crates/atuin-kv/src/store.rs`, `crates/atuin-scripts/src/store.rs` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
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/atuin-dotfiles/src/shell/bash.rs:44— crates/atuin-dotfiles/src/shell/bash.rs:44-57 | crates/atuin-dotfiles/src/shell/fish.rs:45-58 | crates/atuin-dotfiles/src/shell/powershell.rs:45-58 | crates/atuin-dotfiles/src/shell/xonsh.rs:44-57 | crates/atuin-dotfiles/src/shell/zsh.rs:44-57 — 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/atuin-dotfiles/src/store.rs:53— crates/atuin-dotfiles/src/store.rs:53-115 | crates/atuin-dotfiles/src/store/var.rs:47-93 | crates/atuin-kv/src/store/record.rs:34-100 | crates/atuin-scripts/src/store/record.rs:47-89 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (28 lines × 2) crates/atuin-client/src/auth.rs:408— crates/atuin-client/src/auth.rs:408-435 | crates/atuin-client/src/auth.rs:473-500 — 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 (22–26 lines × 2) crates/atuin-ai/src/resume_tui/terminal.rs:193— crates/atuin-ai/src/resume_tui/terminal.rs:193-214 | crates/atuin/src/command/client/search/interactive.rs:1705-1730 — 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 (26 lines × 2) crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:299— crates/atuin-common/src/harnesstools/ccode/rehydrate.rs:299-324 | crates/atuin-common/src/harnesstools/pi/rehydrate.rs:260-285 — `crates/atuin-common/src/harnesstools/ccode/rehydrate.rs` and `crates/atuin-common/src/harnesstools/pi/rehydrate.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 5 separate duplicated blocks between them, totalling at least 54 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 (25 lines × 2) crates/atuin/src/command/client/dotfiles/alias.rs:55— crates/atuin/src/command/client/dotfiles/alias.rs:55-79 | crates/atuin/src/command/client/dotfiles/var.rs:80-104 — 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 (22 lines × 2) crates/atuin-common/src/harnesstools/ccode/session.rs:246— crates/atuin-common/src/harnesstools/ccode/session.rs:246-267 | crates/atuin-common/src/harnesstools/pi/session.rs:430-451 — 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 (21 lines × 2) crates/atuin/src/command/client/store/pull.rs:78— crates/atuin/src/command/client/store/pull.rs:78-98 | crates/atuin/src/command/client/store/push.rs:77-97 — 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 (14–15 lines × 2) crates/atuin-client/src/history/store.rs:62— crates/atuin-client/src/history/store.rs:62-75 | crates/atuin-scripts/src/store/record.rs:18-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12–14 lines × 2) crates/atuin-ai/src/resume_tui/keymap.rs:254— crates/atuin-ai/src/resume_tui/keymap.rs:254-265 | crates/atuin/src/command/client/search/keybindings/defaults.rs:263-276 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 3) crates/atuin-dotfiles/src/store.rs:56— crates/atuin-dotfiles/src/store.rs:56-68 | crates/atuin-dotfiles/src/store/var.rs:50-62 | crates/atuin-scripts/src/store/record.rs:50-62 — before extracting anything, compare `crates/atuin-dotfiles/src/store.rs` and `crates/atuin-dotfiles/src/store/var.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 80 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 (11–12 lines × 2) crates/atuin/src/command/client/account/login.rs:118— crates/atuin/src/command/client/account/login.rs:118-128 | crates/atuin/src/command/client/account/register.rs:73-84 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9–11 lines × 2) crates/atuin-ai/src/resume_tui/state.rs:922— crates/atuin-ai/src/resume_tui/state.rs:922-930 | crates/atuin/src/command/client/search/interactive.rs:411-421 — 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 (10–11 lines × 2) crates/atuin-ai/src/tools/mod.rs:916— crates/atuin-ai/src/tools/mod.rs:916-925 | crates/atuin-ai/src/tools/mod.rs:928-938 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 4) crates/atuin-dotfiles/src/store.rs:54— crates/atuin-dotfiles/src/store.rs:54-62 | crates/atuin-dotfiles/src/store/var.rs:48-56 | crates/atuin-kv/src/store/record.rs:35-43 | crates/atuin-scripts/src/store/record.rs:48-56 — before extracting anything, compare `crates/atuin-dotfiles/src/store.rs` and `crates/atuin-dotfiles/src/store/var.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) crates/atuin-common/src/harnesstools/ccode/session.rs:242— crates/atuin-common/src/harnesstools/ccode/session.rs:242-249 | crates/atuin-common/src/harnesstools/codex/session.rs:257-264 | crates/atuin-common/src/harnesstools/pi/session.rs:426-433 — `crates/atuin-common/src/harnesstools/ccode/session.rs` and `crates/atuin-common/src/harnesstools/codex/session.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 4 separate duplicated blocks between them, totalling at least 38 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 (7–8 lines × 2) crates/atuin-client/src/ai_session/database/heads.rs:491— crates/atuin-client/src/ai_session/database/heads.rs:491-498 | crates/atuin-common/src/harnesstools/rehydrate.rs:384-390 — 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/atuin-client/src/database.rs:385— crates/atuin-client/src/database.rs:385-391 | crates/atuin-kv/src/database.rs:32-38 | crates/atuin-scripts/src/database.rs:32-38 — 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 (13 lines × 4) crates/atuin-dotfiles/src/shell/bash.rs:8— crates/atuin-dotfiles/src/shell/bash.rs:8-20 | crates/atuin-dotfiles/src/shell/fish.rs:9-21 | crates/atuin-dotfiles/src/shell/zsh.rs:8-20 | crates/atuin-dotfiles/src/shell/zsh.rs:22-34 — before extracting anything, compare `crates/atuin-dotfiles/src/shell/bash.rs` and `crates/atuin-dotfiles/src/shell/fish.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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 (10 lines × 5) crates/atuin-dotfiles/src/shell/bash.rs:48— crates/atuin-dotfiles/src/shell/bash.rs:48-57 | crates/atuin-dotfiles/src/shell/fish.rs:49-58 | crates/atuin-dotfiles/src/shell/powershell.rs:49-58 | crates/atuin-dotfiles/src/shell/xonsh.rs:48-57 | crates/atuin-dotfiles/src/shell/zsh.rs:48-57 — before extracting anything, compare `crates/atuin-dotfiles/src/shell/bash.rs` and `crates/atuin-dotfiles/src/shell/fish.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 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.
Interpolated log message defeats structured logging crates/atuin-server/src/settings.rs:123— `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`.
Interpolated log message defeats structured logging crates/atuin-server/src/handlers/user.rs:43— `error!` at line 43 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/atuin-server/src/handlers/user.rs:56— `debug!` at line 56 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `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/atuin-server/src/handlers/user.rs:60— `error!` at line 60 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/atuin-server/src/handlers/user.rs:103— `error!` at line 103 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/atuin-server/src/handlers/user.rs:134— `debug!` at line 134 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/atuin-server/src/handlers/user.rs:138— `error!` at line 138 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/atuin-server/src/handlers/user.rs:168— `error!` at line 168 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/atuin-server/src/handlers/user.rs:192— `error!` at line 192 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/atuin-server/src/handlers/user.rs:202— `debug!` at line 202 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/atuin-server/src/handlers/user.rs:206— `error!` at line 206 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/atuin-server/src/handlers/v0/record.rs:42— `error!` at line 42 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/atuin-server/src/handlers/v0/record.rs:61— `error!` at line 61 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/atuin-server/src/handlers/v0/record.rs:94— `error!` at line 94 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/atuin-server/src/handlers/v0/store.rs:23— `error!` at line 23 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/atuin-server/src/db/mod.rs:446— `debug!` at line 446 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/atuin-scripts/src/database.rs:23— `debug!` at line 23 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/atuin-scripts/src/database.rs:111— `debug!` at line 111 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/atuin-scripts/src/database.rs:168— `debug!` at line 168 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/atuin-scripts/src/database.rs:182— `debug!` at line 182 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/atuin-scripts/src/execution.rs:83— `debug!` at line 83 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/atuin-scripts/src/execution.rs:121— `debug!` at line 121 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/atuin-scripts/src/execution.rs:248— `debug!` at line 248 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/atuin-scripts/src/execution.rs:270— `debug!` at line 270 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/atuin-scripts/src/store.rs:92— `warn!` at line 92 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`.
Duplicated predicate crates/atuin-common/res/harnesstools/opencode/atuin.ts:150— `typeof command !== "string" || command.length === 0` appears character-identically in 3 files — crates/atuin-common/res/harnesstools/opencode/atuin.ts, crates/atuin-common/res/harnesstools/opencode/atuin.v2.ts, crates/atuin-common/res/harnesstools/pi/atuin.ts. 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/atuin-common/res/harnesstools/opencode/atuin.ts:160— `typeof description === "string" && description.length > 0` appears character-identically in 2 files — crates/atuin-common/res/harnesstools/opencode/atuin.ts, crates/atuin-common/res/harnesstools/opencode/atuin.v2.ts. 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/atuin/src/command/client/init/bash.rs:25— `cfg!(feature = "ai") && options.enable_ai_resume` appears character-identically in 2 files — crates/atuin/src/command/client/init/bash.rs, crates/atuin/src/command/client/init/fish.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 REDACTED:504— `host.parent_source_id == row.parent_source_id && turn_base(host) == turn_base(row)` appears character-identically in 2 files — REDACTED, crates/atuin-common/src/harnesstools/opencode/rehydrate/v2.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/atuin-ai/src/resume_tui/state.rs:948— `self.is_insert_mode() && !single.ctrl && !single.alt` appears character-identically in 2 files — crates/atuin-ai/src/resume_tui/state.rs, crates/atuin/src/command/client/search/interactive.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/atuin-ai/src/resume_tui/render.rs:1301— `settings.show_help && (compactness == Compactness::Full || area.height > 1)` appears character-identically in 2 files — crates/atuin-ai/src/resume_tui/render.rs, crates/atuin/src/command/client/search/interactive.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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 32 significant file(s) lose their only recent owner: REDACTED, crates/atuin-common/src/string/highlighted.rs, crates/atuin-common/src/fs/tree_watcher/mod.rs, crates/atuin-daemon/src/output_capture/persistence/blob/fjall/mod.rs, crates/atuin/src/command/client/output/search/writers.rs, crates/atuin-common/src/fs/tree_watcher/tracker.rs, crates/atuin-common/src/string/ellipsis.rs, crates/atuin-daemon/src/output_capture/persistence/mod.rs (+24 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 7 significant file(s) lose their only recent owner: crates/atuin-client/src/ai_session/database.rs, crates/atuin-common/src/harnesstools/opencode/session/v2/tests.rs, crates/atuin-daemon/src/session_capture/message_enricher.rs, crates/atuin-client/src/ai_session/model.rs, crates/atuin-daemon/src/grpc/ai/agent/pb.rs, crates/atuin-daemon/src/grpc/ai/session/pb.rs, crates/atuin-common/res/harnesstools/pi/atuin.ts. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (43 single-owned of 395 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 395 of the 535 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: crates/atuin-common/src/fs/lock.rs, crates/atuin-common/src/string/auto_os_string.rs, crates/atuin-ai/src/fsm/events.rs, crates/atuin-ai/src/tui/slash.rs.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 5 of 15 project(s) overshoot their size bounds, lowering Project Cohesion to 3.3/10. The most over is `crates/atuin-common` (60651 LoC, 358 module-visible types across 38 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D40 · Network Egress Confinement· No network policy · ×1
No network policy — No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need.
No seccomp profile REDACTED:3— The workload runs a container with no seccomp profile in force (neither RuntimeDefault nor a Localhost profile, on the container or the pod), so Kubernetes runs it Unconfined. Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Logging is not universal — Only 9/11 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `crates/atuin-domain`, `crates/atuin-pty-proxy`.
No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
No app-layer HTTPS enforcement detected — This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `Server::builder()` (crates/atuin-daemon/src/server.rs:49).
No security response headers detected — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `Server::builder()` (crates/atuin-daemon/src/server.rs:49).
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
Silent fallback default on Err crates/atuin-common/src/docs.rs:42— `version_segment` turns every `Err` into `"main"` — 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.
Outdated: arboard — `arboard` is locked at 3.6.1 but 3.7.0 is the current stable release on crates.io, and it already satisfies the `"3"` requirement declared in crates/atuin-ai/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p arboard` and commit the updated REDACTED.
Outdated: axoupdater — `axoupdater` is locked at 0.10.0 but 0.10.3 is the current stable release on crates.io, and it already satisfies the `"0.10"` requirement declared in crates/atuin/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p axoupdater` and commit the updated REDACTED.
Outdated: clap_complete_nushell — `clap_complete_nushell` is locked at 4.6.1 but 4.6.2 is the current stable release on crates.io, and it already satisfies the `"4"` requirement declared in crates/atuin/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap_complete_nushell` 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"` requirement declared in crates/atuin-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p config` and commit the updated REDACTED.
Outdated: fjall — `fjall` is locked at 3.1.10 but 3.1.13 is the current stable release on crates.io, and it already satisfies the `"3"` requirement declared in crates/atuin-daemon/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p fjall` and commit the updated REDACTED.
Outdated: fs-err — `fs-err` is locked at 3.3.1 but 3.3.2 is the current stable release on crates.io, and it already satisfies the `"3"` requirement declared in crates/atuin-ai/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p fs-err` and commit the updated REDACTED.
Outdated: futures — `futures` is locked at 0.3.32 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/atuin-ai/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures` and commit the updated REDACTED.
Outdated: futures-util — `futures-util` is locked at 0.3.33 but 0.3.34 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in crates/atuin/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p futures-util` and commit the updated REDACTED.
Outdated: humantime — `humantime` is locked at 2.3.0 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in crates/atuin-common/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p humantime` and commit the updated REDACTED.
Outdated: hyper-util — `hyper-util` is locked at 0.1.20 but 0.1.21 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in crates/atuin-daemon/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p hyper-util` and commit the updated REDACTED.
Outdated: indicatif — `indicatif` is locked at 0.18.4 but 0.18.6 is the current stable release on crates.io, and it already satisfies the `"0.18"` requirement declared in crates/atuin-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indicatif` and commit the updated REDACTED.
Outdated: libc — `libc` is locked at 0.2.190 but 0.2.191 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in crates/atuin-pty-proxy/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p libc` and commit the updated REDACTED.
Outdated: locked-tripwire — `locked-tripwire` is locked at 0.1.1 but 0.1.1002 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in crates/atuin/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p locked-tripwire` and commit the updated REDACTED.
Outdated: metrics — `metrics` is locked at 0.24.3 but 0.24.6 is the current stable release on crates.io, and it already satisfies the `"0.24"` requirement declared in crates/atuin-server/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p metrics` and commit the updated REDACTED.
Outdated: metrics-exporter-prometheus — `metrics-exporter-prometheus` is locked at 0.18.1 but 0.18.3 is the current stable release on crates.io, and it already satisfies the `"0.18"` requirement declared in crates/atuin-server/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p metrics-exporter-prometheus` and commit the updated REDACTED.
Outdated: notify — `notify` is locked at 8.2.0 but 8.2.1 is the current stable release on crates.io, and it already satisfies the `"8"` requirement declared in crates/atuin-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: objc2 — `objc2` is locked at 0.6.4 but 0.6.5 is the current stable release on crates.io, and it already satisfies the `"0.6"` requirement declared in crates/atuin-common/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p objc2` and commit the updated REDACTED.
Outdated: palette — `palette` is locked at 0.7.6 but 0.7.7 is the current stable release on crates.io, and it already satisfies the `"0.7"` requirement declared in crates/atuin-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p palette` and commit the updated REDACTED.
Outdated: prost — `prost` is locked at 0.14.3 but 0.14.4 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in crates/atuin-client/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p prost` and commit the updated REDACTED.
Outdated: prost-types — `prost-types` is locked at 0.14.3 but 0.14.4 is the current stable release on crates.io, and it already satisfies the `"0.14"` requirement declared in crates/atuin-daemon/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p prost-types` and commit the updated REDACTED.
Outdated: pulldown-cmark — `pulldown-cmark` 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/atuin-ai/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p pulldown-cmark` and commit the updated REDACTED.
Outdated: ref-cast — `ref-cast` is locked at 1.0.25 but 1.0.27 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/atuin-common/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ref-cast` and commit the updated REDACTED.
Outdated: regex — `regex` is locked at 1.12.4 but 1.13.1 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/atuin-ai/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p regex` 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/atuin-ai/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p reqwest` and commit the updated REDACTED.
Outdated: rmcp — `rmcp` is locked at 3.3.0 but 3.7.0 is the current stable release on crates.io, and it already satisfies the `"3"` requirement declared in crates/atuin-ai/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rmcp` and commit the updated REDACTED.
Off the main sequence: atuin-common — atuin-common: abstractness 0.17, instability 0.00, distance 0.83 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
runtime-hardening: not applicable — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
Run 01a17602-c46e-7a60-8f94-cc37d558336b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 93 · Warnings: 471 · Recommendations: 67 · Info: 39 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 02:20 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.