Public report of sxyazi/yazi, published 25 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, 25 October 2026, 22:01 UTC · Survey ID cd_9ccddea8dfbf4976846a4feebe695046
sxyazi/yazi
Measured 25 October 2026, 21:53 UTC, at code version 40a9142
No regression since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 67,445 lines of product code in 31 projects, tests not counted · Estimated rebuild effort: about 0.5 person-years · Weakest lens: Event-Driven, 10
Findings by how serious they are
61 critical256 serious19 minor
25 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
25 October 2026, 21:53 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 ▸
52of 52 dimensions measured by tools.
312of 336 findings point to an exact file and line, so you can open each one in the code. The other 24 concern the repository as a whole, such as missing documentation.
52dimensions across 8 lenses, read from 67,445 lines of product code in 31 projects.
sxyazi/yazi falls short of our standard for production because it has message handlers that wait for another service. It scores 44 out of 100 and is rated Weak, and 52 of its 61 critical findings are security problems in the build pipeline.
Event-Driven, at 10, is the weakest lens and counts most in the score. The best first step is stopping the event handlers from waiting on other services, worth about 28 points. Raising Event-Driven to 70 would lift the score to about 70.
Forty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seven secrets can leak from the build pipeline, and five sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, limiting each secret to its own step and making the hidden dependencies explicit would close these risks. The two inner parts of the code that depend on an outer part need turning around so they point inward.
The product code is 67,445 lines, about €68,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.
Dependency direction · Dependency-rule violation: yazi-core (Domain) → yazi-adapter (Infrastructure)
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 28 findings
These 28 critical or serious findings were in the previous survey, on 11 October 2026, and are gone from this one.
€23,000 to €110,000, for 377 to 1,197 hours of work, about 0.5 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 67,445 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
Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 3 points · Low effort · ADR Quality
3
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.
Raises the score by about 3 points · Low effort · Bus Factor
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €68,000 to build again, about 0.5 person-years of work. Its weakest lens is Event-Driven, at 10 (Critical). Event-Driven is about whether the parts of the system can rely on the messages they send each other. Because the weakest lens counts most in the score, work on Event-Driven also moves the score most.
Based on: the rebuild estimate · the Event-Driven grade · how much each lens counts
What to do: Start with the Event-Driven actions in Top priorities.
If you do one thing first · First action
Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place. Of all the actions in this report, it raises the score most for the work it takes: about 28 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.
1046 modules, with 2637 dependencies between them. 13 loops run through 130 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 1006 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.
yazi_actor.lives.ctx uses yazi_actor.lives.ptr, so a change to yazi_actor.lives.ptr can break yazi_actor.lives.ctx, while a change to yazi_actor.lives.ctx can't break yazi_actor.lives.ptr.
Position
Below the diagonal: yazi_actor.lives.ctx uses a module listed above it, which is the healthy direction.
yazi_actor.lives.file uses yazi_actor.lives.ptr, so a change to yazi_actor.lives.ptr can break yazi_actor.lives.file, while a change to yazi_actor.lives.file can't break yazi_actor.lives.ptr.
Position
Below the diagonal: yazi_actor.lives.file uses a module listed above it, which is the healthy direction.
yazi_core.core uses yazi_config.theme.theme, so a change to yazi_config.theme.theme can break yazi_core.core, while a change to yazi_core.core can't break yazi_config.theme.theme.
Position
Below the diagonal: yazi_core.core uses a module listed above it, which is the healthy direction.
yazi_sftp.error uses yazi_shared.auth.display, so a change to yazi_shared.auth.display can break yazi_sftp.error, while a change to yazi_sftp.error can't break yazi_shared.auth.display.
Position
Below the diagonal: yazi_sftp.error uses a module listed above it, which is the healthy direction.
yazi_shared.auth.auth_arc uses yazi_shared.auth.display, so a change to yazi_shared.auth.display can break yazi_shared.auth.auth_arc, while a change to yazi_shared.auth.auth_arc can't break yazi_shared.auth.display.
Position
Below the diagonal: yazi_shared.auth.auth_arc uses a module listed above it, which is the healthy direction.
14→36 yazi_shared.url.traits uses yazi_shared.url.urlpart of a loop✕
Connections
1 pair of types, where a type in yazi_shared.url.traits uses a type in yazi_shared.url.url.
yazi_shared.url.traits uses yazi_shared.url.url, so a change to yazi_shared.url.url can break yazi_shared.url.traits, while a change to yazi_shared.url.traits can't break yazi_shared.url.url.
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.
1 pair of types, where a type in yazi_actor.actor uses a type in yazi_actor.lives.ctx.
The types involved
yazi_actor.actor.Actor → yazi_actor.lives.ctx.Ctx
Direction
yazi_actor.actor uses yazi_actor.lives.ctx, so a change to yazi_actor.lives.ctx can break yazi_actor.actor, while a change to yazi_actor.actor can't break yazi_actor.lives.ctx.
Position
Below the diagonal: yazi_actor.actor uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in yazi_scheduler.worker uses a type in yazi_sftp.id.
The types involved
yazi_scheduler.worker.Worker → yazi_sftp.id.Id
Direction
yazi_scheduler.worker uses yazi_sftp.id, so a change to yazi_sftp.id can break yazi_scheduler.worker, while a change to yazi_scheduler.worker can't break yazi_sftp.id.
Position
Below the diagonal: yazi_scheduler.worker uses a module listed above it, which is the healthy direction.
yazi_scheduler.worker uses yazi_actor.lives.file, so a change to yazi_actor.lives.file can break yazi_scheduler.worker, while a change to yazi_scheduler.worker can't break yazi_actor.lives.file.
Position
Below the diagonal: yazi_scheduler.worker uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in yazi_actor.app.lua uses a type in yazi_actor.lives.ctx.
The types involved
yazi_actor.app.lua.Lua → yazi_actor.lives.ctx.Ctx
Direction
yazi_actor.app.lua uses yazi_actor.lives.ctx, so a change to yazi_actor.lives.ctx can break yazi_actor.app.lua, while a change to yazi_actor.app.lua can't break yazi_actor.lives.ctx.
Position
Below the diagonal: yazi_actor.app.lua uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in yazi_actor.app.lua uses a type in yazi_actor.actor.
The types involved
yazi_actor.app.lua.Lua → yazi_actor.actor.Actor
Direction
yazi_actor.app.lua uses yazi_actor.actor, so a change to yazi_actor.actor can break yazi_actor.app.lua, while a change to yazi_actor.app.lua can't break yazi_actor.actor.
Position
Below the diagonal: yazi_actor.app.lua uses a module listed above it, which is the healthy direction.
yazi_binding.style.style uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_binding.style.style, while a change to yazi_binding.style.style can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_binding.style.style uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in yazi_dds.ember.ember uses a type in yazi_sftp.id.
The types involved
yazi_dds.ember.ember.Ember → yazi_sftp.id.Id
Direction
yazi_dds.ember.ember uses yazi_sftp.id, so a change to yazi_sftp.id can break yazi_dds.ember.ember, while a change to yazi_dds.ember.ember can't break yazi_sftp.id.
Position
Below the diagonal: yazi_dds.ember.ember uses a module listed above it, which is the healthy direction.
yazi_dds.ember.ember uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_dds.ember.ember, while a change to yazi_dds.ember.ember can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_dds.ember.ember uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in yazi_fs.stat.stat uses a type in yazi_actor.app.lua.
The types involved
yazi_fs.stat.stat.Stat → yazi_actor.app.lua.Lua
Direction
yazi_fs.stat.stat uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_fs.stat.stat, while a change to yazi_fs.stat.stat can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_fs.stat.stat uses a module listed above it, which is the healthy direction.
yazi_parser.spark.spark uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_parser.spark.spark, while a change to yazi_parser.spark.spark can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_parser.spark.spark uses a module listed above it, which is the healthy direction.
yazi_shared.data.any uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_shared.data.any, while a change to yazi_shared.data.any can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_shared.data.any uses a module listed above it, which is the healthy direction.
yazi_binding.elements.table uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_binding.elements.table, while a change to yazi_binding.elements.table can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_binding.elements.table uses a module listed above it, which is the healthy direction.
yazi_binding.elements.table uses yazi_binding.style.style, so a change to yazi_binding.style.style can break yazi_binding.elements.table, while a change to yazi_binding.elements.table can't break yazi_binding.style.style.
Position
Below the diagonal: yazi_binding.elements.table uses a module listed above it, which is the healthy direction.
23→26 yazi_binding.elements.table uses yazi_binding.elements.rectpart of a loop✕
Connections
1 pair of types, where a type in yazi_binding.elements.table uses a type in yazi_binding.elements.rect.
yazi_binding.elements.table uses yazi_binding.elements.rect, so a change to yazi_binding.elements.rect can break yazi_binding.elements.table, while a change to yazi_binding.elements.table can't break yazi_binding.elements.rect.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→31 yazi_binding.elements.table uses yazi_binding.elements.areapart of a loop✕
Connections
1 pair of types, where a type in yazi_binding.elements.table uses a type in yazi_binding.elements.area.
yazi_binding.elements.table uses yazi_binding.elements.area, so a change to yazi_binding.elements.area can break yazi_binding.elements.table, while a change to yazi_binding.elements.table can't break yazi_binding.elements.area.
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.
1 pair of types, where a type in yazi_binding.scope uses a type in yazi_actor.app.lua.
The types involved
yazi_binding.scope.Scope → yazi_actor.app.lua.Lua
Direction
yazi_binding.scope uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_binding.scope, while a change to yazi_binding.scope can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_binding.scope uses a module listed above it, which is the healthy direction.
yazi_binding.scope uses yazi_shared.data.any, so a change to yazi_shared.data.any can break yazi_binding.scope, while a change to yazi_binding.scope can't break yazi_shared.data.any.
Position
Below the diagonal: yazi_binding.scope uses a module listed above it, which is the healthy direction.
yazi_fs.engine.attrs uses yazi_binding.time.duration, so a change to yazi_binding.time.duration can break yazi_fs.engine.attrs, while a change to yazi_fs.engine.attrs can't break yazi_binding.time.duration.
Position
Below the diagonal: yazi_fs.engine.attrs uses a module listed above it, which is the healthy direction.
yazi_fs.engine.attrs uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_fs.engine.attrs, while a change to yazi_fs.engine.attrs can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_fs.engine.attrs uses a module listed above it, which is the healthy direction.
yazi_fs.engine.attrs uses yazi_fs.stat.stat, so a change to yazi_fs.stat.stat can break yazi_fs.engine.attrs, while a change to yazi_fs.engine.attrs can't break yazi_fs.stat.stat.
Position
Below the diagonal: yazi_fs.engine.attrs uses a module listed above it, which is the healthy direction.
yazi_binding.elements.rect uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_binding.elements.rect, while a change to yazi_binding.elements.rect can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_binding.elements.rect uses a module listed above it, which is the healthy direction.
yazi_binding.elements.rect uses yazi_shared.data.any, so a change to yazi_shared.data.any can break yazi_binding.elements.rect, while a change to yazi_binding.elements.rect can't break yazi_shared.data.any.
Position
Below the diagonal: yazi_binding.elements.rect uses a module listed above it, which is the healthy direction.
yazi_binding.elements.rect uses yazi_binding.elements.table, so a change to yazi_binding.elements.table can break yazi_binding.elements.rect, while a change to yazi_binding.elements.rect can't break yazi_binding.elements.table.
Position
Below the diagonal: yazi_binding.elements.rect uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in yazi_sftp.packet uses a type in yazi_fs.stat.stat.
The types involved
yazi_sftp.packet.Packet → yazi_fs.stat.stat.Stat
Direction
yazi_sftp.packet uses yazi_fs.stat.stat, so a change to yazi_fs.stat.stat can break yazi_sftp.packet, while a change to yazi_sftp.packet can't break yazi_fs.stat.stat.
Position
Below the diagonal: yazi_sftp.packet uses a module listed above it, which is the healthy direction.
yazi_sftp.packet uses yazi_fs.engine.attrs, so a change to yazi_fs.engine.attrs can break yazi_sftp.packet, while a change to yazi_sftp.packet can't break yazi_fs.engine.attrs.
Position
Below the diagonal: yazi_sftp.packet uses a module listed above it, which is the healthy direction.
27→29 yazi_sftp.packet uses yazi_sftp.responses.datapart of a loop✕
Connections
1 pair of types, where a type in yazi_sftp.packet uses a type in yazi_sftp.responses.data.
yazi_sftp.packet uses yazi_sftp.responses.data, so a change to yazi_sftp.responses.data can break yazi_sftp.packet, while a change to yazi_sftp.packet can't break yazi_sftp.responses.data.
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.
yazi_binding.position.position uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_binding.position.position, while a change to yazi_binding.position.position can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_binding.position.position uses a module listed above it, which is the healthy direction.
yazi_binding.position.position uses yazi_binding.elements.table, so a change to yazi_binding.elements.table can break yazi_binding.position.position, while a change to yazi_binding.position.position can't break yazi_binding.elements.table.
Position
Below the diagonal: yazi_binding.position.position uses a module listed above it, which is the healthy direction.
yazi_binding.position.position uses yazi_binding.elements.rect, so a change to yazi_binding.elements.rect can break yazi_binding.position.position, while a change to yazi_binding.position.position can't break yazi_binding.elements.rect.
Position
Below the diagonal: yazi_binding.position.position uses a module listed above it, which is the healthy direction.
28→31 yazi_binding.position.position uses yazi_binding.elements.areapart of a loop✕
Connections
1 pair of types, where a type in yazi_binding.position.position uses a type in yazi_binding.elements.area.
yazi_binding.position.position uses yazi_binding.elements.area, so a change to yazi_binding.elements.area can break yazi_binding.position.position, while a change to yazi_binding.position.position can't break yazi_binding.elements.area.
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.
yazi_sftp.responses.data uses yazi_sftp.packet, so a change to yazi_sftp.packet can break yazi_sftp.responses.data, while a change to yazi_sftp.responses.data can't break yazi_sftp.packet.
Position
Below the diagonal: yazi_sftp.responses.data uses a module listed above it, which is the healthy direction.
yazi_widgets.input.input uses yazi_shared.event.action_cow, so a change to yazi_shared.event.action_cow can break yazi_widgets.input.input, while a change to yazi_widgets.input.input can't break yazi_shared.event.action_cow.
Position
Below the diagonal: yazi_widgets.input.input uses a module listed above it, which is the healthy direction.
yazi_widgets.input.input uses yazi_binding.elements.rect, so a change to yazi_binding.elements.rect can break yazi_widgets.input.input, while a change to yazi_widgets.input.input can't break yazi_binding.elements.rect.
Position
Below the diagonal: yazi_widgets.input.input uses a module listed above it, which is the healthy direction.
yazi_binding.elements.area uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_binding.elements.area, while a change to yazi_binding.elements.area can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_binding.elements.area uses a module listed above it, which is the healthy direction.
yazi_binding.elements.area uses yazi_binding.elements.rect, so a change to yazi_binding.elements.rect can break yazi_binding.elements.area, while a change to yazi_binding.elements.area can't break yazi_binding.elements.rect.
Position
Below the diagonal: yazi_binding.elements.area uses a module listed above it, which is the healthy direction.
yazi_binding.elements.area uses yazi_binding.position.position, so a change to yazi_binding.position.position can break yazi_binding.elements.area, while a change to yazi_binding.elements.area can't break yazi_binding.position.position.
Position
Below the diagonal: yazi_binding.elements.area uses a module listed above it, which is the healthy direction.
yazi_shared.strand.buf uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_shared.strand.buf, while a change to yazi_shared.strand.buf can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_shared.strand.buf uses a module listed above it, which is the healthy direction.
yazi_shared.strand.buf uses yazi_sftp.responses.data, so a change to yazi_sftp.responses.data can break yazi_shared.strand.buf, while a change to yazi_shared.strand.buf can't break yazi_sftp.responses.data.
Position
Below the diagonal: yazi_shared.strand.buf uses a module listed above it, which is the healthy direction.
32→33 yazi_shared.strand.buf uses yazi_shared.strand.strandpart of a loop✕
Connections
1 pair of types, where a type in yazi_shared.strand.buf uses a type in yazi_shared.strand.strand.
yazi_shared.strand.buf uses yazi_shared.strand.strand, so a change to yazi_shared.strand.strand can break yazi_shared.strand.buf, while a change to yazi_shared.strand.buf can't break yazi_shared.strand.strand.
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.
32→34 yazi_shared.strand.buf uses yazi_shared.path.pathpart of a loop✕
Connections
1 pair of types, where a type in yazi_shared.strand.buf uses a type in yazi_shared.path.path.
yazi_shared.strand.buf uses yazi_shared.path.path, so a change to yazi_shared.path.path can break yazi_shared.strand.buf, while a change to yazi_shared.strand.buf can't break yazi_shared.path.path.
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.
yazi_shared.strand.strand uses yazi_shared.strand.buf, so a change to yazi_shared.strand.buf can break yazi_shared.strand.strand, while a change to yazi_shared.strand.strand can't break yazi_shared.strand.buf.
Position
Below the diagonal: yazi_shared.strand.strand uses a module listed above it, which is the healthy direction.
yazi_shared.path.path uses yazi_shared.auth.display, so a change to yazi_shared.auth.display can break yazi_shared.path.path, while a change to yazi_shared.path.path can't break yazi_shared.auth.display.
Position
Below the diagonal: yazi_shared.path.path uses a module listed above it, which is the healthy direction.
yazi_shared.path.path uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_shared.path.path, while a change to yazi_shared.path.path can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_shared.path.path uses a module listed above it, which is the healthy direction.
yazi_shared.path.path uses yazi_shared.strand.strand, so a change to yazi_shared.strand.strand can break yazi_shared.path.path, while a change to yazi_shared.path.path can't break yazi_shared.strand.strand.
Position
Below the diagonal: yazi_shared.path.path uses a module listed above it, which is the healthy direction.
34→35 yazi_shared.path.path uses yazi_shared.path.bufpart of a loop✕
Connections
1 pair of types, where a type in yazi_shared.path.path uses a type in yazi_shared.path.buf.
yazi_shared.path.path uses yazi_shared.path.buf, so a change to yazi_shared.path.buf can break yazi_shared.path.path, while a change to yazi_shared.path.path can't break yazi_shared.path.buf.
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.
yazi_shared.path.buf uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_shared.path.buf, while a change to yazi_shared.path.buf can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_shared.path.buf uses a module listed above it, which is the healthy direction.
yazi_shared.path.buf uses yazi_shared.strand.buf, so a change to yazi_shared.strand.buf can break yazi_shared.path.buf, while a change to yazi_shared.path.buf can't break yazi_shared.strand.buf.
Position
Below the diagonal: yazi_shared.path.buf uses a module listed above it, which is the healthy direction.
yazi_shared.path.buf uses yazi_shared.strand.strand, so a change to yazi_shared.strand.strand can break yazi_shared.path.buf, while a change to yazi_shared.path.buf can't break yazi_shared.strand.strand.
Position
Below the diagonal: yazi_shared.path.buf uses a module listed above it, which is the healthy direction.
yazi_shared.path.buf uses yazi_shared.path.path, so a change to yazi_shared.path.path can break yazi_shared.path.buf, while a change to yazi_shared.path.buf can't break yazi_shared.path.path.
Position
Below the diagonal: yazi_shared.path.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.url uses yazi_shared.auth.display, so a change to yazi_shared.auth.display can break yazi_shared.url.url, while a change to yazi_shared.url.url can't break yazi_shared.auth.display.
Position
Below the diagonal: yazi_shared.url.url uses a module listed above it, which is the healthy direction.
yazi_shared.url.url uses yazi_actor.lives.file, so a change to yazi_actor.lives.file can break yazi_shared.url.url, while a change to yazi_shared.url.url can't break yazi_actor.lives.file.
Position
Below the diagonal: yazi_shared.url.url uses a module listed above it, which is the healthy direction.
yazi_shared.url.url uses yazi_shared.auth.auth_arc, so a change to yazi_shared.auth.auth_arc can break yazi_shared.url.url, while a change to yazi_shared.url.url can't break yazi_shared.auth.auth_arc.
Position
Below the diagonal: yazi_shared.url.url uses a module listed above it, which is the healthy direction.
yazi_shared.url.url uses yazi_shared.url.traits, so a change to yazi_shared.url.traits can break yazi_shared.url.url, while a change to yazi_shared.url.url can't break yazi_shared.url.traits.
Position
Below the diagonal: yazi_shared.url.url uses a module listed above it, which is the healthy direction.
yazi_shared.url.url uses yazi_shared.strand.strand, so a change to yazi_shared.strand.strand can break yazi_shared.url.url, while a change to yazi_shared.url.url can't break yazi_shared.strand.strand.
Position
Below the diagonal: yazi_shared.url.url uses a module listed above it, which is the healthy direction.
yazi_shared.url.url uses yazi_shared.path.path, so a change to yazi_shared.path.path can break yazi_shared.url.url, while a change to yazi_shared.url.url can't break yazi_shared.path.path.
Position
Below the diagonal: yazi_shared.url.url uses a module listed above it, which is the healthy direction.
36→39 yazi_shared.url.url uses yazi_shared.url.bufpart of a loop✕
Connections
1 pair of types, where a type in yazi_shared.url.url uses a type in yazi_shared.url.buf.
yazi_shared.url.url uses yazi_shared.url.buf, so a change to yazi_shared.url.buf can break yazi_shared.url.url, while a change to yazi_shared.url.url can't break yazi_shared.url.buf.
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.
yazi_shared.url.like uses yazi_shared.auth.display, so a change to yazi_shared.auth.display can break yazi_shared.url.like, while a change to yazi_shared.url.like can't break yazi_shared.auth.display.
Position
Below the diagonal: yazi_shared.url.like uses a module listed above it, which is the healthy direction.
yazi_shared.url.like uses yazi_shared.auth.auth_arc, so a change to yazi_shared.auth.auth_arc can break yazi_shared.url.like, while a change to yazi_shared.url.like can't break yazi_shared.auth.auth_arc.
Position
Below the diagonal: yazi_shared.url.like uses a module listed above it, which is the healthy direction.
yazi_shared.url.like uses yazi_shared.strand.strand, so a change to yazi_shared.strand.strand can break yazi_shared.url.like, while a change to yazi_shared.url.like can't break yazi_shared.strand.strand.
Position
Below the diagonal: yazi_shared.url.like uses a module listed above it, which is the healthy direction.
yazi_shared.url.like uses yazi_shared.path.path, so a change to yazi_shared.path.path can break yazi_shared.url.like, while a change to yazi_shared.url.like can't break yazi_shared.path.path.
Position
Below the diagonal: yazi_shared.url.like uses a module listed above it, which is the healthy direction.
yazi_shared.url.like uses yazi_shared.url.url, so a change to yazi_shared.url.url can break yazi_shared.url.like, while a change to yazi_shared.url.like can't break yazi_shared.url.url.
Position
Below the diagonal: yazi_shared.url.like uses a module listed above it, which is the healthy direction.
37→39 yazi_shared.url.like uses yazi_shared.url.bufpart of a loop✕
Connections
1 pair of types, where a type in yazi_shared.url.like uses a type in yazi_shared.url.buf.
yazi_shared.url.like uses yazi_shared.url.buf, so a change to yazi_shared.url.buf can break yazi_shared.url.like, while a change to yazi_shared.url.like can't break yazi_shared.url.buf.
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.
yazi_shared.url.cow uses yazi_shared.auth.display, so a change to yazi_shared.auth.display can break yazi_shared.url.cow, while a change to yazi_shared.url.cow can't break yazi_shared.auth.display.
Position
Below the diagonal: yazi_shared.url.cow uses a module listed above it, which is the healthy direction.
yazi_shared.url.cow uses yazi_shared.auth.auth_arc, so a change to yazi_shared.auth.auth_arc can break yazi_shared.url.cow, while a change to yazi_shared.url.cow can't break yazi_shared.auth.auth_arc.
Position
Below the diagonal: yazi_shared.url.cow uses a module listed above it, which is the healthy direction.
yazi_shared.url.cow uses yazi_shared.url.traits, so a change to yazi_shared.url.traits can break yazi_shared.url.cow, while a change to yazi_shared.url.cow can't break yazi_shared.url.traits.
Position
Below the diagonal: yazi_shared.url.cow uses a module listed above it, which is the healthy direction.
yazi_shared.url.cow uses yazi_sftp.responses.data, so a change to yazi_sftp.responses.data can break yazi_shared.url.cow, while a change to yazi_shared.url.cow can't break yazi_sftp.responses.data.
Position
Below the diagonal: yazi_shared.url.cow uses a module listed above it, which is the healthy direction.
yazi_shared.url.cow uses yazi_shared.path.path, so a change to yazi_shared.path.path can break yazi_shared.url.cow, while a change to yazi_shared.url.cow can't break yazi_shared.path.path.
Position
Below the diagonal: yazi_shared.url.cow uses a module listed above it, which is the healthy direction.
yazi_shared.url.cow uses yazi_shared.url.url, so a change to yazi_shared.url.url can break yazi_shared.url.cow, while a change to yazi_shared.url.cow can't break yazi_shared.url.url.
Position
Below the diagonal: yazi_shared.url.cow uses a module listed above it, which is the healthy direction.
yazi_shared.url.cow uses yazi_shared.url.like, so a change to yazi_shared.url.like can break yazi_shared.url.cow, while a change to yazi_shared.url.cow can't break yazi_shared.url.like.
Position
Below the diagonal: yazi_shared.url.cow uses a module listed above it, which is the healthy direction.
38→39 yazi_shared.url.cow uses yazi_shared.url.bufpart of a loop✕
Connections
1 pair of types, where a type in yazi_shared.url.cow uses a type in yazi_shared.url.buf.
yazi_shared.url.cow uses yazi_shared.url.buf, so a change to yazi_shared.url.buf can break yazi_shared.url.cow, while a change to yazi_shared.url.cow can't break yazi_shared.url.buf.
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.
yazi_shared.url.buf uses yazi_shared.auth.display, so a change to yazi_shared.auth.display can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_shared.auth.display.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_actor.lives.file, so a change to yazi_actor.lives.file can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_actor.lives.file.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_shared.auth.auth_arc, so a change to yazi_shared.auth.auth_arc can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_shared.auth.auth_arc.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_shared.url.traits, so a change to yazi_shared.url.traits can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_shared.url.traits.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_actor.app.lua, so a change to yazi_actor.app.lua can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_actor.app.lua.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_shared.data.any, so a change to yazi_shared.data.any can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_shared.data.any.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_binding.elements.table, so a change to yazi_binding.elements.table can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_binding.elements.table.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_sftp.responses.data, so a change to yazi_sftp.responses.data can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_sftp.responses.data.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_shared.path.buf, so a change to yazi_shared.path.buf can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_shared.path.buf.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_shared.url.url, so a change to yazi_shared.url.url can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_shared.url.url.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_shared.url.like, so a change to yazi_shared.url.like can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_shared.url.like.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_shared.url.buf uses yazi_shared.url.cow, so a change to yazi_shared.url.cow can break yazi_shared.url.buf, while a change to yazi_shared.url.buf can't break yazi_shared.url.cow.
Position
Below the diagonal: yazi_shared.url.buf uses a module listed above it, which is the healthy direction.
yazi_fs.engine.traits uses yazi_actor.lives.file, so a change to yazi_actor.lives.file can break yazi_fs.engine.traits, while a change to yazi_fs.engine.traits can't break yazi_actor.lives.file.
Position
Below the diagonal: yazi_fs.engine.traits uses a module listed above it, which is the healthy direction.
yazi_fs.engine.traits uses yazi_shared.url.traits, so a change to yazi_shared.url.traits can break yazi_fs.engine.traits, while a change to yazi_fs.engine.traits can't break yazi_shared.url.traits.
Position
Below the diagonal: yazi_fs.engine.traits uses a module listed above it, which is the healthy direction.
yazi_fs.engine.traits uses yazi_fs.engine.attrs, so a change to yazi_fs.engine.attrs can break yazi_fs.engine.traits, while a change to yazi_fs.engine.traits can't break yazi_fs.engine.attrs.
Position
Below the diagonal: yazi_fs.engine.traits uses a module listed above it, which is the healthy direction.
yazi_fs.engine.traits uses yazi_shared.path.buf, so a change to yazi_shared.path.buf can break yazi_fs.engine.traits, while a change to yazi_fs.engine.traits can't break yazi_shared.path.buf.
Position
Below the diagonal: yazi_fs.engine.traits uses a module listed above it, which is the healthy direction.
yazi_fs.engine.traits uses yazi_shared.url.url, so a change to yazi_shared.url.url can break yazi_fs.engine.traits, while a change to yazi_fs.engine.traits can't break yazi_shared.url.url.
Position
Below the diagonal: yazi_fs.engine.traits uses a module listed above it, which is the healthy direction.
yazi_fs.engine.traits uses yazi_shared.url.buf, so a change to yazi_shared.url.buf can break yazi_fs.engine.traits, while a change to yazi_fs.engine.traits can't break yazi_shared.url.buf.
Position
Below the diagonal: yazi_fs.engine.traits uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
53
High / Critical
A03:2025 — Software Supply Chain Failures
11
Medium
Roadmap
First, eliminate handler temporal coupling by moving awaited work off the synchronous handler using async spawning. Next, address static analysis findings by fixing secret exposure in the CI workflow files, particularly REDACTED. Then, document significant design decisions as Architecture Decision Records to preserve institutional knowledge and mitigate off-boarding risks.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place.
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.
Per-file score 0–10 — a quality signature. Of 155 files carrying findings, judged against the Production bar: 1% slop · 35% mixed · 64% near-clean.
File
Score
Band
Worst signal
REDACTED
2.3
Slop
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
yazi-adapter/src/drivers/kgp.rs
5.5
Mixed
Code Duplication: Near-duplicate member pair (41 shared lines)
REDACTED
5.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.9
Mixed
Dependency Vulnerabilities: Medium CVE: REDACTED
yazi-fs/src/stat/mode.rs
6.0
Mixed
Explicit Debt: TodoComment
yazi-binding/src/process/child.rs
6.0
Mixed
Explicit Debt: TodoComment
yazi-watcher/src/local/local.rs
6.0
Mixed
Explicit Debt: TodoComment
yazi-actor/src/mgr/bulk_create.rs
6.0
Mixed
Explicit Debt: TodoComment
yazi-scheduler/src/worker.rs
6.3
Mixed
Code Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens)
yazi-core/src/highlighter.rs
6.7
Mixed
Explicit Debt: TodoComment
yazi-fs/src/trash/freedesktop/trash.rs
6.7
Mixed
Explicit Debt: FixmeComment
yazi-plugin/src/fs/fs.rs
6.7
Mixed
Explicit Debt: TodoComment
yazi-shared/src/url/buf.rs
6.7
Mixed
Explicit Debt: FixmeComment
yazi-adapter/src/drivers/iip.rs
7.0
Mixed
Code Duplication: Duplicated block (11 lines × 2)
yazi-scheduler/src/file/out.rs
7.1
Mixed
Code Duplication: Members sharing a duplicated core (5 members, 50+ identical tokens)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 61
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 — 256
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 — 19
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 25
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. 52 of 52 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 — 52 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, 312 of 336 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, 26 test files), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
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 no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust, lua 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 no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust, lua is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Lua, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Kotlin, Scala, Go, Swift, Python and Ruby source only, and no C# was loaded, no Java, Kotlin, Scala, Go, Swift, Python or Ruby was found, and this repository's Lua 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.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's Rust calls level macros (`info!`, `warn!`, …) the reading cannot place in `tracing` or `log` — its crate depends on both, imports them through a `#[macro_use]` at the crate root, or logs through `slog` — so its log calls cannot be judged, 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.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Lua, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
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.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
22 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Executor::mgr at 64. A further 33 function(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 Spark::into_lua at 134 — they are counted neither in the figure above nor in this dimension's score. 22 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: yazi-parser/src/spark/spark.rs (Spark::into_lua at 134), yazi-term/src/event/keyboard.rs (KeyCode::from_kitty_codepoint at 65), yazi-plugin/src/utils/utils.rs (yazi_plugin::utils::utils::compose::get at 52), yazi-shim/src/fs/serde.rs (yazi_shim::fs::serde::kind_from_str at 40), yazi-plugin/src/ui/ui.rs (yazi_plugin::ui::ui::compose::get at 31), and 17 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 15 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 22 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Executor::mgr (cyclomatic 64), Key::from_str (cyclomatic 46), yazi_shared::shell::unix::split (cyclomatic 44). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 22 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
+ 26 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 7 bodies over 30 down to 30 or less in Cognitive Complexity — start with Server::make (cognitive 65), Executor::mgr (cognitive 61), Entries::update_existing (cognitive 47). — 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 7 together lifts Cognitive Complexity from 6.5 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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.6 / 10Stronggated by 6 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.
Resolve the 4 TooManyMethods finding(s) in God Classes — start with utils.rs, input.rs, parser.rs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 MethodTooLong finding(s) in God Classes — start with spark.rs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TooManyFunctions finding(s) in God Classes — start with engine.rs. — One of this dimension's main actionable groups (1 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.
100 duplicated block group(s) detected. A further 8 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 37 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with kgp.rs (2), hidden.rs, drivers.rs. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 11 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with de.rs (2), buf.rs (2), chan.rs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 7 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with de.rs, display.rs, traits.rs. — One of this dimension's main actionable groups (7 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.1 / 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.
31 production modules (Cargo), 0 dependency cycle(s), 2 unstable depended-on module(s). Read from the build's own module declarations; 5 module(s) off the main sequence, with abstractness counted on 27 of the 31 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: yazi-sftp · ×5
Unstable project yazi-parser
Unstable project yazi-plugin
What to do
Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Unstable project yazi-parser finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project yazi-plugin finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with operator.rs, worker.rs, action.rs. — One of this dimension's main actionable groups (4 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
83 test methods: 83 unit, 0 integration, 0 BDD, 0 e2e. The Rust suite contributes 83 `#[test]` function(s) across 26 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 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.
2 outdated, 1 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Yanked release: clipboard-win
Outdated: notify · ×2
What to do
Resolve the 1 Yanked release finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 526 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 1 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: yazi-parser/src/spark/spark.rs (9×134=1206); yazi-plugin/src/utils/utils.rs (10×52=520); yazi-fm/src/executor.rs (6×64=384) Repeated repair below the complexity floor: yazi-adapter/src/adapter.rs (3 of 5 changes were fixes); yazi-fs/src/trash/freedesktop/trash.rs (3 of 4 changes were fixes)
Resolve the 23 Hotspot finding(s) in Churn × Complexity Hotspots — start with spark.rs, utils.rs, executor.rs. — One of this dimension's main actionable groups (23 warning-level).
Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with adapter.rs, trash.rs. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor3.5 / 10Weak✓ 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.
170 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is yazi-shared/src/url/buf.rs. Counted over 262 of the 1350 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
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
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.
32 deducted task-comment markers across 67445 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 22 TodoComment finding(s) in Explicit Debt — start with local.rs, packet.rs, layer.rs. — One of this dimension's main actionable groups (22 warning-level).
Resolve the 10 FixmeComment finding(s) in Explicit Debt — start with buf.rs (2), reporter.rs, loc.rs. — One of this dimension's main actionable groups (10 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. 34 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.
3 of 31 build units (Cargo) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
53 finding(s): 0 critical, 52 high, 1 medium, 0 low. 44 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. Separately, one or more rules could not re-parse an embedded snippet in 1 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
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
No action in Static Analysis (SAST) — all 41 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (41 issue-level, 0 of them charged here).
No action in Static Analysis (SAST) — all 3 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (3 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 2 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Medium CVE 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.
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.
2 of 262 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is yazi-shared/src/translit/table.rs. Counted over 262 of the 1350 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 5 Boundary-crossing change coupling finding(s) in Change Coupling — start with mod.rs, boot.rs, mux.rs. — One of this dimension's main actionable groups (5 issue-level).
Resolve the 5 Change coupling finding(s) in Change Coupling — start with payload.rs, slim.rs, iip.rs. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with kgp.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.
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 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
`yazi-core` is a Domain project but references `yazi-adapter`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
`yazi-core` is a Domain project but references `yazi-tui`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether an aggregate references another aggregate by identity rather than embedding it by object reference.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
Other · Domain Modelling — Whether domain identifiers are strongly typed (a newtype wrapper) rather than raw primitives — consistency once an idiom exists.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
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 · Event-Driven — Whether event/message handlers avoid synchronous blocking waits — a blocking wait inside a handler stalls throughput and risks deadlock.
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
`Copy.act` is an event/message handler that blocks the executor on a synchronous wait (`block_on`/`blocking_recv`/`thread::sleep`/a blocking `recv()`) — it stalls the handler and serialises throughput, and on an async runtime can starve the reactor. Either move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`, if the result isn't needed inline) or make the handler itself `async` so it can `.await`. (×2) — yazi-actor/src/mgr/copy.rs:18, yazi-actor/src/spot/copy.rs:17
What to do
Move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`) or make the handler `async` so it can `.await` — a sync handler cannot simply `.await` in place.
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.
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.
Do you agree with this assessment?
P2 · Observability6.7 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 19/21 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `yazi-build`, `yazi-cli`.
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 `cargo` — add that `package-ecosystem` entry to .github/dependabot.yml 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.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · 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 `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `RefCell` it is walking alone — safe Rust rejects a body that changes the collection its loop borrows at compile time, except through interior mutability: a `RefCell` borrowed in the loop's header stays borrowed until the loop ends, so a `borrow_mut()` of it inside the body panics with `already borrowed: BorrowMutError` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 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 — 4 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 — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 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.
AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — ~512 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; Rust not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (yazi-core), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
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 — Not assessed, and this one is on us: 125 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (2 aggregate(s) with Apply/When folds)
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
S1 Web-Security Posture — No web surface: 1347 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
X12 Unreachable branch — 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
X13 Undrained process stream — 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
X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X17 Uncapped recursion over a caller-supplied document — not 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
X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X19 Unrestored process-global state — not 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
X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — 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
X23 Unguarded diagnostic materialisation — 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
X24 Document value interpolated into markup unescaped — 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
X25 Inert configuration knob — 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
X26 Unsynchronised callback handoff — 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
X3 Exception handling — 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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — 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
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: mod.rs ↔ executor.rs yazi-actor/src/mgr/mod.rs:1— `yazi-actor/src/mgr/mod.rs` (context yazi-actor) and `yazi-fm/src/executor.rs` (context yazi-fm) sit in DIFFERENT parts of the tree yet change together 92% of the time (12 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `519939b5` feat: new `visual_arrow` action to reanchor visual selections (#4281); `fde56338` feat: bulk create (#3793); `c703332b` feat: new `bulk_exit` action that customizes the prompt for bulk oper… — run `git show` on any of them.
Boundary-crossing change coupling: boot.rs ↔ xdg.rs yazi-boot/src/boot.rs:1— `yazi-boot/src/boot.rs` (context yazi-boot) and `yazi-fs/src/xdg.rs` (context yazi-fs) sit in DIFFERENT parts of the tree yet change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `62dd22b8` fix: put package cache in cache dir instead of state dir (#3930); `a109aa92` refactor: refine URN for archives (#3043); `4d8e276a` feat: flavor (#753) (at that commit the file was still `yazi-shared/src/xdg.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: mux.rs ↔ term.rs yazi-emulator/src/mux.rs:1— `yazi-emulator/src/mux.rs` (context yazi-emulator) and `yazi-term/src/term.rs` (context yazi-term) sit in DIFFERENT parts of the tree yet change together 69% of the time (9 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) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `a076ff8c` refactor: satisfy `mismatched-lifetime-syntaxes` lint (#2881) (at that commit the files were still `yazi-adapter/src/mux.rs` and `yazi-fm/src/term.rs`); `8ed569b7` refactor: move `tty` to the new `yazi-term` crate (#2701) (at that commit the files were still `yazi-adapter/src/mux.rs` and `yazi-fm/src/term.rs`); `119cc9c2` feat: support using Yazi in Helix directly without Zellij or tmux (#2… (at that commit the files were still `yazi-adapter/src/mux.rs` and `yazi-fm/src/term.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: lib.rs ↔ mux.rs yazi-adapter/src/lib.rs:1— `yazi-adapter/src/lib.rs` (context yazi-adapter) and `yazi-emulator/src/mux.rs` (context yazi-emulator) sit in DIFFERENT parts of the tree yet change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a076ff8c` refactor: satisfy `mismatched-lifetime-syntaxes` lint (#2881) (at that commit the file was still `yazi-adapter/src/mux.rs`); `119cc9c2` feat: support using Yazi in Helix directly without Zellij or tmux (#2… (at that commit the file was still `yazi-adapter/src/mux.rs`); `f25ef0f0` feat: terminal response detection under async stdin (#2347) (at that commit the file was still `yazi-adapter/src/mux.rs`) — run `git show` on any of them.
Boundary-crossing change coupling: open.rs ↔ prework.rs yazi-actor/src/mgr/open.rs:1— `yazi-actor/src/mgr/open.rs` (context yazi-actor) and `yazi-core/src/tasks/prework.rs` (context yazi-core) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `e795d6cf` feat: offload mimetype fetching on opening files to the task schedule… (at that commit the file was still `yazi-core/src/tasks/preload.rs`); `4194befb` feat: true custom `mime` fetcher support - using user rules even duri… (at that commit the files were still `yazi-core/src/manager/commands/open.rs` and `yazi-core/src/tasks/preload.rs`); `61c0db86` fix: set a dedicated `Mimetype` agency to reconcile regular files and… (at that commit the files were still `yazi-core/src/manager/commands/open.rs` and `yazi-core/src/tasks/preload.rs`) — run `git show` on any of them.
Dependency-rule violation: yazi-core (Domain) → yazi-adapter (Infrastructure) — `yazi-core` is a Domain project but references `yazi-adapter`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Dependency-rule violation: yazi-core (Domain) → yazi-tui (Web) — `yazi-core` is a Domain project but references `yazi-tui`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Blocking wait inside a handler: Copy.act yazi-actor/src/mgr/copy.rs:18— `Copy.act` is an event/message handler that blocks the executor on a synchronous wait (`block_on`/`blocking_recv`/`thread::sleep`/a blocking `recv()`) — it stalls the handler and serialises throughput, and on an async runtime can starve the reactor. Either move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`, if the result isn't needed inline) or make the handler itself `async` so it can `.await`.
Blocking wait inside a handler: Copy.act yazi-actor/src/spot/copy.rs:17— `Copy.act` is an event/message handler that blocks the executor on a synchronous wait (`block_on`/`blocking_recv`/`thread::sleep`/a blocking `recv()`) — it stalls the handler and serialises throughput, and on an async runtime can starve the reactor. Either move the awaited work off the handler (`tokio::spawn`/`Handle::current().spawn`, if the result isn't needed inline) or make the handler itself `async` so it can `.await`.
Hotspot: yazi-parser/src/spark/spark.rs yazi-parser/src/spark/spark.rs:206— yazi-parser/src/spark/spark.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 134 in Spark::into_lua at line 206. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-parser/src/spark/spark.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: yazi-plugin/src/utils/utils.rs yazi-plugin/src/utils/utils.rs:6— yazi-plugin/src/utils/utils.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in yazi_plugin::utils::utils::compose at line 6. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-plugin/src/utils/utils.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: yazi-fm/src/executor.rs yazi-fm/src/executor.rs:66— yazi-fm/src/executor.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in Executor::mgr at line 66. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-fm/src/executor.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: yazi-plugin/src/fs/fs.rs yazi-plugin/src/fs/fs.rs:13— yazi-plugin/src/fs/fs.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in yazi_plugin::fs::fs::compose at line 13. 1 of those changes was a fix/bug commit, 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-plugin/src/fs/fs.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: yazi-watcher/src/refresher.rs yazi-watcher/src/refresher.rs:43— yazi-watcher/src/refresher.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Refresher::handle at line 43. 4 of those changes were fix/bug commits, and the other 7 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-watcher/src/refresher.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: yazi-term/src/parser/csi.rs yazi-term/src/parser/csi.rs:9— yazi-term/src/parser/csi.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 32 in Parser::parse_csi at line 9. 2 of those changes were fix/bug commits, and the other 4 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-term/src/parser/csi.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: yazi-core/src/tab/folder.rs yazi-core/src/tab/folder.rs:65— yazi-core/src/tab/folder.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Folder::update at line 65. 2 of those changes were fix/bug commits, and the other 7 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-core/src/tab/folder.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: yazi-adapter/src/drivers/drivers.rs yazi-adapter/src/drivers/drivers.rs:42— yazi-adapter/src/drivers/drivers.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in Drivers::from at line 42. 1 of those changes was a fix/bug commit, and the other 7 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-adapter/src/drivers/drivers.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: yazi-binding/src/process/child.rs yazi-binding/src/process/child.rs:88— yazi-binding/src/process/child.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Child::add_methods at line 88. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-binding/src/process/child.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: yazi-fs/src/entries.rs yazi-fs/src/entries.rs:172— yazi-fs/src/entries.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in Entries::update_existing at line 172. 1 of those changes was a fix/bug commit, and the other 4 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-fs/src/entries.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: yazi-cli/src/main.rs yazi-cli/src/main.rs:31— yazi-cli/src/main.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in yazi_cli::run at line 31. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-cli/src/main.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: yazi-scheduler/src/file/file.rs yazi-scheduler/src/file/file.rs:79— yazi-scheduler/src/file/file.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in File::r#move at line 79. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-scheduler/src/file/file.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: yazi-fs/src/engine/capabilities.rs yazi-fs/src/engine/capabilities.rs:73— yazi-fs/src/engine/capabilities.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Capabilities::set at line 73. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-fs/src/engine/capabilities.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: yazi-scheduler/src/file/in.rs yazi-scheduler/src/file/in.rs:105— yazi-scheduler/src/file/in.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in FileIn::into_doable at line 105. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-scheduler/src/file/in.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: yazi-dds/src/payload.rs yazi-dds/src/payload.rs:89— yazi-dds/src/payload.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in Payload::fmt at line 89. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-dds/src/payload.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: yazi-dds/src/ember/ember.rs yazi-dds/src/ember/ember.rs:33— yazi-dds/src/ember/ember.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in Ember::from_str at line 33. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-dds/src/ember/ember.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: yazi-actor/src/mgr/copy.rs yazi-actor/src/mgr/copy.rs:18— yazi-actor/src/mgr/copy.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Copy::act at line 18. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-actor/src/mgr/copy.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: yazi-scheduler/src/file/traverse.rs yazi-scheduler/src/file/traverse.rs:131— yazi-scheduler/src/file/traverse.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in yazi_scheduler::file::traverse::traverse at line 131. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-scheduler/src/file/traverse.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: yazi-fs/src/sorter.rs yazi-fs/src/sorter.rs:20— yazi-fs/src/sorter.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in FilesSorter::sort at line 20. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-fs/src/sorter.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: yazi-emulator/src/brand.rs yazi-emulator/src/brand.rs:53— yazi-emulator/src/brand.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in Brand::from_env at line 53. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-emulator/src/brand.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: yazi-binding/src/process/command.rs yazi-binding/src/process/command.rs:113— yazi-binding/src/process/command.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Command::add_methods at line 113. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-binding/src/process/command.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: yazi-fs/src/stat/mode.rs yazi-fs/src/stat/mode.rs:93— yazi-fs/src/stat/mode.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in StatMode::permissions 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-fs/src/stat/mode.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: yazi-tty/src/lua.rs yazi-tty/src/lua.rs:9— yazi-tty/src/lua.rs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in Tty::queue at line 9. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-tty/src/lua.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.
TodoComment yazi-watcher/src/local/local.rs:89— // TODO: revert this once a new notification is implemented — 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 yazi-sftp/src/packet.rs:257— // TODO: use Vec<u8> — 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 yazi-plugin/src/utils/layer.rs:82— // 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 yazi-binding/src/elements/table.rs:27— // 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 yazi-actor/src/spot/copy.rs:29— // 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 yazi-plugin/src/utils/preview.rs:12— // 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 yazi-plugin/src/fs/fs.rs:18— // TODO: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment yazi-binding/src/macros.rs:215— // TODO: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment yazi-binding/src/elements/border.rs:74— // TODO: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment yazi-binding/src/elements/border_type.rs:47— // TODO: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment yazi-fs/src/stat/mode.rs:155— // TODO: deprecate — 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 yazi-fs/src/mounts/linux.rs:118— // TODO: mount.external — 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 yazi-fs/src/engine/local/dir_entry.rs:30— // TODO: use `file_name_os_str` when stabilized — 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 yazi-core/src/highlighter.rs:270— // TODO: When ansi_term adds support for bright variants using codes — 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 yazi-core/src/which/sorter.rs:56— // TODO: remove the `mem::take` since that involves Arc atomics refcount changes — 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 yazi-cli/src/package/git.rs:72— // TODO: compat for old caches, remove in the future — 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 yazi-binding/src/process/child.rs:124— // TODO: deprecate this method — 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 yazi-binding/src/position/lua.rs:45— // TODO: cache — 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 yazi-binding/src/elements/text.rs:17— // TODO: block — 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 yazi-adapter/src/icc.rs:19— // TODO: Use `create_transform_in_place_nbit` in the next minor version of moxcms. — 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 yazi-actor/src/tasks/inspect.rs:53— // TODO: stdin — 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 yazi-actor/src/mgr/bulk_create.rs:68— // TODO: support `bulk_exit`? — 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.
Duplicated block (5 lines × 2) yazi-actor/src/mgr/hidden.rs:39— yazi-actor/src/mgr/hidden.rs:39-43 | yazi-actor/src/mgr/sort.rs:47-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) yazi-adapter/src/drivers/drivers.rs:25— yazi-adapter/src/drivers/drivers.rs:25-29 | yazi-adapter/src/drivers/drivers.rs:31-35 — 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) yazi-adapter/src/drivers/kgp.rs:376— yazi-adapter/src/drivers/kgp.rs:376-380 | yazi-adapter/src/drivers/kgp_old.rs:77-81 — before extracting anything, compare `yazi-adapter/src/drivers/kgp.rs` and `yazi-adapter/src/drivers/kgp_old.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 (5 lines × 2) yazi-adapter/src/drivers/kgp.rs:400— yazi-adapter/src/drivers/kgp.rs:400-404 | yazi-adapter/src/drivers/kgp_old.rs:100-104 — before extracting anything, compare `yazi-adapter/src/drivers/kgp.rs` and `yazi-adapter/src/drivers/kgp_old.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 (5 lines × 2) yazi-binding/src/elements/line.rs:115— yazi-binding/src/elements/line.rs:115-119 | yazi-binding/src/elements/text.rs:154-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) yazi-binding/src/http/session.rs:51— yazi-binding/src/http/session.rs:51-55 | yazi-vfs/src/engine/rw_file.rs:180-184 — 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) yazi-config/src/plugin/fetchers.rs:75— yazi-config/src/plugin/fetchers.rs:75-79 | yazi-config/src/plugin/preloaders.rs:79-83 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) yazi-config/src/keymap/chord.rs:106— yazi-config/src/keymap/chord.rs:106-110 | yazi-config/src/opener/opener_rule_matcher.rs:46-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) yazi-binding/src/process/child.rs:177— yazi-binding/src/process/child.rs:177-182 | yazi-binding/src/process/child.rs:186-190 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) yazi-term/src/parser/csi.rs:70— yazi-term/src/parser/csi.rs:70-74 | yazi-term/src/parser/csi.rs:142-146 — 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) yazi-binding/src/http/response.rs:90— yazi-binding/src/http/response.rs:90-94 | yazi-binding/src/process/command.rs:194-198 — 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) yazi-scheduler/src/file/file.rs:63— yazi-scheduler/src/file/file.rs:63-67 | yazi-scheduler/src/file/file.rs:143-147 — 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) yazi-shared/src/url/buf.rs:28— yazi-shared/src/url/buf.rs:28-32 | yazi-shared/src/url/cow.rs:17-21 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) yazi-vfs/src/engine/file_cursor.rs:15— yazi-vfs/src/engine/file_cursor.rs:15-19 | yazi-vfs/src/engine/file_cursor.rs:25-29 — 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) yazi-watcher/src/local/local.rs:90— yazi-watcher/src/local/local.rs:90-94 | yazi-watcher/src/virtual/virtual.rs:34-38 — 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) yazi-binding/src/chan.rs:34— yazi-binding/src/chan.rs:34-39 | yazi-binding/src/chan.rs:58-63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) yazi-binding/src/elements/line.rs:41— yazi-binding/src/elements/line.rs:41-46 | yazi-binding/src/elements/text.rs:29-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) yazi-config/src/open/open_rules.rs:118— yazi-config/src/open/open_rules.rs:118-123 | yazi-config/src/plugin/previewers.rs:118-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) yazi-shared/src/data/de.rs:110— yazi-shared/src/data/de.rs:110-115 | yazi-shared/src/data/de_owned.rs:113-118 — 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) yazi-shared/src/natsort.rs:23— yazi-shared/src/natsort.rs:23-28 | yazi-shared/src/natsort.rs:47-52 — 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) yazi-binding/src/elements/area.rs:92— yazi-binding/src/elements/area.rs:92-97 | yazi-binding/src/elements/row.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) yazi-shared/src/path/buf.rs:95— yazi-shared/src/path/buf.rs:95-100 | yazi-shared/src/path/path.rs:65-70 — 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) yazi-shared/src/path/buf.rs:103— yazi-shared/src/path/buf.rs:103-108 | yazi-shared/src/path/path.rs:73-78 — 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) yazi-shared/src/data/de.rs:297— yazi-shared/src/data/de.rs:297-302 | yazi-shared/src/data/de_owned.rs:302-307 — 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) yazi-vfs/src/engine/demand.rs:75— yazi-vfs/src/engine/demand.rs:75-80 | yazi-vfs/src/engine/demand.rs:93-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) yazi-runner/src/loader/loader.rs:122— yazi-runner/src/loader/loader.rs:122-127 | yazi-runner/src/loader/loader.rs:160-165 — 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.
FixmeComment yazi-watcher/src/reporter.rs:33— // FIXME: LINKED should return Url instead of Path — 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.
FixmeComment yazi-shared/src/url/buf.rs:17— // FIXME: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment yazi-shared/src/loc/buf.rs:23— // FIXME: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment yazi-shared/src/loc/loc.rs:39— // FIXME: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment yazi-config/src/theme/theme.rs:49— // FIXME: remove — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment yazi-shared/src/data/data.rs:280— // FIXME: find a better name — 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.
FixmeComment yazi-scheduler/src/size/size.rs:38— // FIXME: use PathBufDyn instead of UrlBuf in SizeIn — 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.
FixmeComment yazi-fs/src/trash/freedesktop/trash.rs:123— // FIXME: also rename or remove the .trashinfo file in the info folder — 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.
FixmeComment yazi-dds/src/pubsub.rs:125— // FIXME: handle error — 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.
FixmeComment yazi-actor/src/mgr/bulk_create.rs:98— // log_if_err!(Pubsub::pub_after_bulk_create(it)); // FIXME — 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.
Duplicated block (9 lines × 2) yazi-shared/src/auth/de.rs:123— yazi-shared/src/auth/de.rs:123-131 | yazi-shared/src/url/de.rs:96-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) yazi-shared/src/auth/display.rs:42— yazi-shared/src/auth/display.rs:42-50 | yazi-shared/src/auth/encode.rs:35-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) yazi-shim/src/mlua/traits.rs:52— yazi-shim/src/mlua/traits.rs:52-60 | yazi-shim/src/mlua/traits.rs:93-101 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) yazi-watcher/src/refresher.rs:54— yazi-watcher/src/refresher.rs:54-62 | yazi-watcher/src/refresher.rs:70-78 — 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) yazi-config/src/open/open_rule_matcher.rs:41— yazi-config/src/open/open_rule_matcher.rs:41-49 | yazi-config/src/opener/opener_rule_matcher.rs:32-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) yazi-actor/src/mgr/enter.rs:24— yazi-actor/src/mgr/enter.rs:24-32 | yazi-actor/src/mgr/leave.rs:26-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) yazi-plugin/src/fs/fs.rs:98— yazi-plugin/src/fs/fs.rs:98-106 | yazi-plugin/src/fs/fs.rs:227-235 — 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) yazi-actor/src/mgr/hidden.rs:28— yazi-actor/src/mgr/hidden.rs:28-35 | yazi-actor/src/mgr/sort.rs:35-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) yazi-adapter/src/drivers/kgp.rs:326— yazi-adapter/src/drivers/kgp.rs:326-333 | yazi-adapter/src/drivers/kgp_old.rs:27-34 — before extracting anything, compare `yazi-adapter/src/drivers/kgp.rs` and `yazi-adapter/src/drivers/kgp_old.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) yazi-binding/src/elements/row.rs:20— yazi-binding/src/elements/row.rs:20-27 | yazi-binding/src/elements/table.rs:37-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) yazi-fs/src/engine/local/calculator.rs:37— yazi-fs/src/engine/local/calculator.rs:37-44 | yazi-vfs/src/engine/calculator.rs:37-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) yazi-config/src/plugin/fetchers.rs:99— yazi-config/src/plugin/fetchers.rs:99-106 | yazi-config/src/plugin/preloaders.rs:103-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) yazi-vfs/src/engine/sftp/conn.rs:130— yazi-vfs/src/engine/sftp/conn.rs:130-137 | yazi-vfs/src/engine/sftp/conn.rs:164-172 — 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) yazi-actor/src/mgr/bulk_create.rs:126— yazi-actor/src/mgr/bulk_create.rs:126-133 | yazi-actor/src/mgr/bulk_rename.rs:171-178 — 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) yazi-actor/src/mgr/tab_close.rs:31— yazi-actor/src/mgr/tab_close.rs:31-37 | yazi-actor/src/mgr/tab_switch.rs:29-35 — 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) yazi-adapter/src/drivers/kgp.rs:358— yazi-adapter/src/drivers/kgp.rs:358-364 | yazi-adapter/src/drivers/kgp_old.rs:59-65 — before extracting anything, compare `yazi-adapter/src/drivers/kgp.rs` and `yazi-adapter/src/drivers/kgp_old.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 (7 lines × 2) yazi-scheduler/src/file/file.rs:27— yazi-scheduler/src/file/file.rs:27-33 | yazi-scheduler/src/file/file.rs:80-86 — 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) yazi-sftp/src/requests/mkdir.rs:16— yazi-sftp/src/requests/mkdir.rs:16-22 | yazi-sftp/src/requests/set_stat.rs:18-41 — 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) yazi-config/src/opener/opener.rs:59— yazi-config/src/opener/opener.rs:59-65 | yazi-config/src/vfs/authorities.rs:42-48 — 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) yazi-shared/src/strand/buf.rs:80— yazi-shared/src/strand/buf.rs:80-86 | yazi-shared/src/strand/strand.rs:152-158 — 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) yazi-sftp/src/fs/attrs.rs:109— yazi-sftp/src/fs/attrs.rs:109-115 | yazi-sftp/src/responses/extended.rs:51-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Change coupling: payload.rs ↔ pubsub.rs yazi-dds/src/payload.rs:1— `yazi-dds/src/payload.rs` and `yazi-dds/src/pubsub.rs` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 `99ed93d3` feat: new `theme` DDS event for plugins to watch theme reloads (#4203); `fde56338` feat: bulk create (#3793); `31cfc581` feat: new `download` DDS event fires when remote files are downloaded… — run `git show` on any of them.
Change coupling: slim.rs ↔ standard.rs yazi-plugin/src/slim.rs:1— `yazi-plugin/src/slim.rs` and `yazi-plugin/src/standard.rs` change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 9 shared commits counted here, the most recent 3 are `16d20e21` feat: new `Path.os()` API creates an OS-native `Path` (#3541) (at that commit the files were still `yazi-plugin/src/isolate/isolate.rs` and `yazi-plugin/src/lua.rs`); `e7cd6637` fix: avoid UI-dependent async APIs from being called during app initi… (at that commit the files were still `yazi-plugin/src/isolate/isolate.rs` and `yazi-plugin/src/lua.rs`); `ac7718c2` feat: new experimental `ya.async()` API (#3422) (at that commit the files were still `yazi-plugin/src/isolate/isolate.rs` and `yazi-plugin/src/lua.rs`) — run `git show` on any of them.
Change coupling: iip.rs ↔ sixel.rs yazi-adapter/src/drivers/iip.rs:1— `yazi-adapter/src/drivers/iip.rs` and `yazi-adapter/src/drivers/sixel.rs` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 `f6113d38` feat: advanced app overall style (#4023); `66d12da0` perf: add `BufWriter` to `Stderr` to avoid frequent system calls and … (at that commit the files were still `yazi-adaptor/src/iterm2.rs` and `yazi-adaptor/src/sixel.rs`); `80aebda2` feat: fix all dependencies to specific version numbers to allow non-`… (at that commit the files were still `yazi-adaptor/src/iterm2.rs` and `yazi-adaptor/src/sixel.rs`) — run `git show` on any of them.
Change coupling: create.rs ↔ rename.rs yazi-actor/src/mgr/create.rs:1— `yazi-actor/src/mgr/create.rs` and `yazi-actor/src/mgr/rename.rs` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 9 shared commits counted here, the most recent 3 are `a3e9ea0d` refactor: generalize `Loc`, `LocBuf`, `Uri`, and `Urn` (#3295); `c2a94daa` feat: casefold (#3114); `0054cf0b` perf: lock-free hashing for string interns (#3091) — run `git show` on any of them.
Change coupling: show.rs ↔ trigger.rs yazi-actor/src/cmp/show.rs:1— `yazi-actor/src/cmp/show.rs` and `yazi-actor/src/cmp/trigger.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 5 shared commits counted here, the most recent 3 are `366fca6b` perf: raise the max allowed concurrent connections per SFTP service (…; `da97e5a8` feat: URL covariance for the mimetype agency (#3030); `ffc635e4` feat: improve path auto-completion results (#2765) (at that commit the files were still `yazi-core/src/cmp/commands/show.rs` and `yazi-core/src/cmp/commands/trigger.rs`) — run `git show` on any of them.
Off the main sequence: yazi-sftp — yazi-sftp: abstractness 0.04, instability 0.00, distance 0.96 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: yazi-term — yazi-term: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: yazi-tty — yazi-tty: abstractness 0.02, instability 0.20, distance 0.78 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: yazi-ffi — yazi-ffi: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: yazi-binding — yazi-binding: abstractness 0.02, instability 0.28, distance 0.70 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
TooManyMethods: Utils yazi-plugin/src/utils/utils.rs:4— TooManyMethods — 57 methods, declared across 20 files: utils/sync.rs (9), utils/text.rs (6), utils/layer.rs (5), utils/user.rs (5), +16 more file(s). The bar is 30 methods; this is 27 over it, 1.90× 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: Input yazi-widgets/src/input/input.rs:13— TooManyMethods — 40 methods, declared across 20 files: input/input.rs (15), actor/kill.rs (3), actor/replace.rs (3), actor/recall.rs (2), +16 more file(s). The bar is 30 methods; this is 10 over it, 1.33× 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: Parser yazi-term/src/parser/parser.rs:9— TooManyMethods — 38 methods, declared across 6 files: parser/parser.rs (22), parser/csi.rs (8), parser/report.rs (4), parser/osc.rs (2), +2 more file(s). The bar is 30 methods; this is 8 over it, 1.27× 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: Url yazi-shared/src/url/url.rs:10— TooManyMethods — 37 methods, declared across 2 files: url/url.rs (36), url/encode.rs (1). The bar is 30 methods; this is 7 over it, 1.23× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) yazi-adapter/src/drivers/chafa.rs:72— yazi-adapter/src/drivers/chafa.rs:72-84 | yazi-adapter/src/drivers/iip.rs:29-41 | yazi-adapter/src/drivers/kgp.rs:335-350 | yazi-adapter/src/drivers/sixel.rs:35-47 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) yazi-scheduler/src/fetch/progress.rs:11— yazi-scheduler/src/fetch/progress.rs:11-21 | yazi-scheduler/src/plugin/progress.rs:12-22 | yazi-scheduler/src/process/progress.rs:68-78 | yazi-scheduler/src/size/progress.rs:11-21 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) yazi-scheduler/src/file/out.rs:63— yazi-scheduler/src/file/out.rs:63-77 | yazi-scheduler/src/file/out.rs:142-156 | yazi-scheduler/src/file/out.rs:404-418 | yazi-scheduler/src/file/out.rs:475-489 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) yazi-scheduler/src/file/progress.rs:21— yazi-scheduler/src/file/progress.rs:21-31 | yazi-scheduler/src/file/progress.rs:67-77 | yazi-scheduler/src/file/progress.rs:254-264 | yazi-scheduler/src/file/progress.rs:300-310 — 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 (15 lines × 2) yazi-core/src/highlighter.rs:101— yazi-core/src/highlighter.rs:101-115 | yazi-core/src/highlighter.rs:129-143 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) yazi-parser/src/mgr/cd.rs:22— yazi-parser/src/mgr/cd.rs:22-36 | yazi-parser/src/mgr/reveal.rs:22-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 (15 lines × 2) yazi-parser/src/cmp/show.rs:12— yazi-parser/src/cmp/show.rs:12-26 | yazi-parser/src/input/show.rs:12-26 — 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 (15 lines × 2) yazi-parser/src/help/close.rs:12— yazi-parser/src/help/close.rs:12-26 | yazi-parser/src/input/close.rs:12-26 — 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 × 2) yazi-scheduler/src/file/out.rs:335— yazi-scheduler/src/file/out.rs:335-347 | yazi-scheduler/src/preload/out.rs:19-31 — 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 × 2) yazi-shared/src/auth/display.rs:52— yazi-shared/src/auth/display.rs:52-64 | yazi-shared/src/auth/encode.rs:45-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) yazi-parser/src/help/toggle.rs:12— yazi-parser/src/help/toggle.rs:12-24 | yazi-parser/src/mgr/tab_close.rs:12-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) yazi-parser/src/app/quit.rs:14— yazi-parser/src/app/quit.rs:14-30 | yazi-parser/src/mgr/close.rs:14-26 — 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 lines × 2) yazi-adapter/src/drivers/kgp.rs:366— yazi-adapter/src/drivers/kgp.rs:366-375 | yazi-adapter/src/drivers/kgp_old.rs:67-76 — before extracting anything, compare `yazi-adapter/src/drivers/kgp.rs` and `yazi-adapter/src/drivers/kgp_old.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 × 2) yazi-fs/src/remover/remover.rs:29— yazi-fs/src/remover/remover.rs:29-38 | yazi-vfs/src/remover/remover.rs:28-37 — 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 lines × 2) yazi-fs/src/splatter.rs:90— yazi-fs/src/splatter.rs:90-99 | yazi-fs/src/splatter.rs:123-132 — 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) yazi-scheduler/src/process/progress.rs:13— yazi-scheduler/src/process/progress.rs:13-22 | yazi-scheduler/src/process/progress.rs:41-50 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Low cohesion: Operator (LCOM4 17) yazi-sftp/src/operator.rs:8— Operator's methods fall into 17 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 17 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Worker (LCOM4 10) yazi-scheduler/src/worker.rs:11— Worker's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Action (LCOM4 8) yazi-shared/src/event/action.rs:11— Action's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: File (LCOM4 5) yazi-vfs/src/engine/lua/file.rs:16— File's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplicated block (14 lines × 2) yazi-adapter/src/drivers/kgp.rs:382— yazi-adapter/src/drivers/kgp.rs:382-395 | yazi-adapter/src/drivers/kgp_old.rs:83-96 — before extracting anything, compare `yazi-adapter/src/drivers/kgp.rs` and `yazi-adapter/src/drivers/kgp_old.rs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 49 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 (14 lines × 2) yazi-config/src/keymap/chords.rs:27— yazi-config/src/keymap/chords.rs:27-40 | yazi-config/src/opener/opener_rules.rs:24-37 — 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 (14 lines × 2) yazi-fs/src/splatter.rs:95— yazi-fs/src/splatter.rs:95-108 | yazi-fs/src/splatter.rs:161-174 — 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 × 3) yazi-config/src/plugin/fetchers.rs:139— yazi-config/src/plugin/fetchers.rs:139-144 | yazi-config/src/plugin/preloaders.rs:143-148 | yazi-config/src/plugin/spotters.rs:120-125 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) yazi-fs/src/xdg.rs:32— yazi-fs/src/xdg.rs:32-37 | yazi-fs/src/xdg.rs:53-58 | yazi-fs/src/xdg.rs:74-79 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 3) yazi-actor/src/app/clipboard.rs:21— yazi-actor/src/app/clipboard.rs:21-26 | yazi-actor/src/app/dnd.rs:21-26 | yazi-actor/src/app/mouse.rs:22-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 3) yazi-binding/src/elements/color.rs:12— yazi-binding/src/elements/color.rs:12-16 | yazi-binding/src/elements/span.rs:24-28 | yazi-binding/src/style/style.rs:26-30 — 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 (5 lines × 3) yazi-dds/src/ember/delete.rs:31— yazi-dds/src/ember/delete.rs:31-35 | yazi-dds/src/ember/download.rs:31-35 | yazi-dds/src/ember/trash.rs:31-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 3) yazi-term/src/parser/csi.rs:69— yazi-term/src/parser/csi.rs:69-73 | yazi-term/src/parser/csi.rs:141-145 | yazi-term/src/parser/csi.rs:172-176 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Key::from_str (cyclomatic 46) yazi-config/src/keymap/key.rs:72— Key::from_str has cyclomatic complexity 46 (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.
Key::fmt (cyclomatic 43) yazi-config/src/keymap/key.rs:146— Key::fmt has cyclomatic complexity 43 (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.
Entries::update_existing (cyclomatic 27) yazi-fs/src/entries.rs:172— Entries::update_existing has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Entries::update_create (cyclomatic 16) yazi-fs/src/entries.rs:119— Entries::update_create 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.
Repeated repair: yazi-adapter/src/adapter.rs yazi-adapter/src/adapter.rs:42— yazi-adapter/src/adapter.rs changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is Adapter::image_hide at line 42), 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: make terminal probe timeout earlier to startup (#4432)”; “fix: wait for terminal probe echo back before stopping instance (#4271)”; “fix: avoid flicker caused by screen clear on final response from terminal (#4250)”. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-adapter/src/adapter.rs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: yazi-fs/src/trash/freedesktop/trash.rs yazi-fs/src/trash/freedesktop/trash.rs:32— yazi-fs/src/trash/freedesktop/trash.rs changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is Trash::entry at line 32), 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: tolerate non-conforming orphaned trash items on Linux (#4343)”; “fix: refresh file list after deleting a file from search view (#4174)”; “fix: reconcile selected and yanked file states on a full list update (#4161)”. 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-25..2026-10-23, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-25 12:35:42 +08:00' --until='2026-10-23 12:35:42 +08:00' --full-history --no-merges -- yazi-fs/src/trash/freedesktop/trash.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.
Entries::update_existing (cognitive 47) yazi-fs/src/entries.rs:172— Entries::update_existing has cognitive complexity 47 (threshold 15). Drivers by points: if/else 18 (33 pts), boolean chains 9, loops 3 (5 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.
Entries::update_create (cognitive 24) yazi-fs/src/entries.rs:119— Entries::update_create has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
yazi_shared::shell::unix::split (cognitive 47) yazi-shared/src/shell/unix.rs:44— yazi_shared::shell::unix::split has cognitive complexity 47 (threshold 15). Drivers by points: match/switch 9 (24 pts), if/else 5 (17 pts), boolean chains 5, 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.
yazi_shared::natsort::natsort (cognitive 21) yazi-shared/src/natsort.rs:67— yazi_shared::natsort::natsort has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (5 pts), boolean chains 2, match/switch 1 (2 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.
SizeCalculator::next_chunk (cognitive 24) yazi-fs/src/engine/local/calculator.rs:75— SizeCalculator::next_chunk has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SizeCalculator::next_chunk (cognitive 19) yazi-vfs/src/engine/calculator.rs:53— SizeCalculator::next_chunk 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.
yazi_fs::engine::local::absolute::try_absolute_impl (cognitive 21) yazi-fs/src/engine/local/absolute.rs:14— yazi_fs::engine::local::absolute::try_absolute_impl has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 3 (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.
yazi_fs::path::clean::clean_path_impl (cognitive 17) yazi-fs/src/path/clean.rs:20— yazi_fs::path::clean::clean_path_impl has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), match/switch 2 (5 pts), loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
Input::r#move (cognitive 21) yazi-widgets/src/input/actor/move.rs:8— Input::r#move has cognitive complexity 21 (threshold 15). Drivers by points: if/else 15 (20 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.
Input::execute (cognitive 19) yazi-widgets/src/input/actor/actor.rs:8— Input::execute has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16 (18 pts), match/switch 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.
File::r#move (cognitive 17) yazi-scheduler/src/file/file.rs:79— File::r#move has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 4, loops 2 (3 pts), match/switch 2 (3 pts) (nesting depth added 2). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
File::add_methods (cognitive 16) yazi-actor/src/lives/file.rs:49— File::add_methods has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×2
REDACTED
REDACTED
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
Duplicated block (11 lines × 2) yazi-adapter/src/drivers/iip.rs:17— yazi-adapter/src/drivers/iip.rs:17-27 | yazi-adapter/src/drivers/sixel.rs:23-33 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) yazi-binding/src/http/part.rs:63— yazi-binding/src/http/part.rs:63-73 | yazi-binding/src/http/session.rs:45-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 4) yazi-scheduler/src/fetch/progress.rs:12— yazi-scheduler/src/fetch/progress.rs:12-21 | yazi-scheduler/src/plugin/progress.rs:13-22 | yazi-scheduler/src/process/progress.rs:69-78 | yazi-scheduler/src/size/progress.rs:12-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (10 lines × 4) yazi-scheduler/src/file/progress.rs:22— yazi-scheduler/src/file/progress.rs:22-31 | yazi-scheduler/src/file/progress.rs:68-77 | yazi-scheduler/src/file/progress.rs:255-264 | yazi-scheduler/src/file/progress.rs:301-310 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) yazi-scheduler/src/custom/progress.rs:18— yazi-scheduler/src/custom/progress.rs:18-27 | yazi-scheduler/src/file/progress.rs:143-152 | yazi-scheduler/src/file/progress.rs:184-193 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (10 lines × 3) yazi-scheduler/src/file/progress.rs:109— yazi-scheduler/src/file/progress.rs:109-118 | yazi-scheduler/src/file/progress.rs:219-228 | yazi-scheduler/src/preload/progress.rs:13-22 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) yazi-config/src/opener/opener.rs:119— yazi-config/src/opener/opener.rs:119-128 | yazi-config/src/vfs/domains_arc.rs:55-63 | yazi-config/src/vfs/vfs.rs:83-91 — 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 (9 lines × 3) yazi-core/src/app/quit.rs:20— yazi-core/src/app/quit.rs:20-28 | yazi-core/src/notify/option.rs:28-36 | yazi-parser/src/mgr/sort.rs:20-28 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) yazi-adapter/src/drivers/chafa.rs:78— yazi-adapter/src/drivers/chafa.rs:78-84 | yazi-adapter/src/drivers/iip.rs:35-41 | yazi-adapter/src/drivers/sixel.rs:41-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (7 lines × 3) yazi-scheduler/src/fetch/in.rs:26— yazi-scheduler/src/fetch/in.rs:26-32 | yazi-scheduler/src/plugin/in.rs:28-34 | yazi-scheduler/src/preload/in.rs:25-31 — 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 (5 lines × 4) yazi-binding/src/http/session.rs:52— yazi-binding/src/http/session.rs:52-56 | yazi-binding/src/process/child.rs:141-145 | yazi-binding/src/process/child.rs:150-155 | yazi-vfs/src/engine/rw_file.rs:197-201 — there are 4 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (5 lines × 4) yazi-adapter/src/drivers/chafa.rs:73— yazi-adapter/src/drivers/chafa.rs:73-77 | yazi-adapter/src/drivers/iip.rs:30-34 | yazi-adapter/src/drivers/kgp.rs:336-340 | yazi-adapter/src/drivers/sixel.rs:36-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Executor::mgr (cyclomatic 64) yazi-fm/src/executor.rs:66— Executor::mgr has cyclomatic complexity 64 (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.
yazi_shared::shell::unix::split (cyclomatic 44) yazi-shared/src/shell/unix.rs:44— yazi_shared::shell::unix::split has cyclomatic complexity 44 (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.
Parser::parse_csi (cyclomatic 32) yazi-term/src/parser/csi.rs:9— Parser::parse_csi has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FilesSorter::sort (cyclomatic 31) yazi-fs/src/sorter.rs:20— FilesSorter::sort has cyclomatic complexity 31 (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.
WordWrapper::process_input (cyclomatic 26) yazi-shim/src/ratatui/wrapper.rs:54— WordWrapper::process_input has cyclomatic complexity 26 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Data::from_lua (cyclomatic 23) yazi-shared/src/data/lua.rs:10— Data::from_lua has cyclomatic complexity 23 (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.
yazi_tui::backend::write_modifier_diff (cyclomatic 23) yazi-tui/src/backend.rs:119— yazi_tui::backend::write_modifier_diff has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StatMode::permissions (cyclomatic 23) yazi-fs/src/stat/mode.rs:93— StatMode::permissions has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Server::make (cyclomatic 22) yazi-dds/src/server.rs:18— Server::make 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.
Child::add_methods (cyclomatic 21) yazi-binding/src/process/child.rs:88— Child::add_methods has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
Refresher::handle (cyclomatic 21) yazi-watcher/src/refresher.rs:43— Refresher::handle has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Input::execute (cyclomatic 19) yazi-widgets/src/input/actor/actor.rs:8— Input::execute has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
yazi_cli::run (cyclomatic 18) yazi-cli/src/main.rs:31— yazi_cli::run has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
Copy::act (cyclomatic 16) yazi-actor/src/mgr/copy.rs:18— Copy::act 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.
Line::add_methods (cyclomatic 16) yazi-binding/src/elements/line.rs:123— Line::add_methods has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
yazi_scheduler::file::traverse::traverse (cyclomatic 16) yazi-scheduler/src/file/traverse.rs:131— yazi_scheduler::file::traverse::traverse has cyclomatic complexity 16 (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.
Attrs::serialize (cyclomatic 16) yazi-sftp/src/fs/attrs.rs:42— Attrs::serialize 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.
Encoder::encode (cyclomatic 16) yazi-shared/src/wire/encoder.rs:13— Encoder::encode 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.
Yanked release: clipboard-win — `clipboard-win` resolves to 5.4.1 in the committed REDACTED, and crates.io reports that release as YANKED. A yanked release is one the publisher has withdrawn and asked you to stop using; it keeps resolving only so existing locks do not break. The current stable release is 5.4.3. Run `cargo update -p clipboard-win` and commit the updated lock.
Server::make (cognitive 65) yazi-dds/src/server.rs:18— Server::make has cognitive complexity 65 (threshold 15). Drivers by points: if/else 16 (58 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Executor::mgr (cognitive 61) yazi-fm/src/executor.rs:66— Executor::mgr has cognitive complexity 61 (threshold 15). Drivers by points: if/else 60, match/switch 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FilesSorter::sort (cognitive 40) yazi-fs/src/sorter.rs:20— FilesSorter::sort has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (27 pts), match/switch 10 (13 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.
WordWrapper::process_input (cognitive 39) yazi-shim/src/ratatui/wrapper.rs:54— WordWrapper::process_input has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 11, loops 2 (4 pts) (nesting depth added 13). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
StatMode::permissions (cognitive 38) yazi-fs/src/stat/mode.rs:93— StatMode::permissions has cognitive complexity 38 (threshold 15). Drivers by points: if/else 31 (37 pts), match/switch 1 (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.
yazi_scheduler::file::traverse::traverse (cognitive 27) yazi-scheduler/src/file/traverse.rs:131— yazi_scheduler::file::traverse::traverse has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (7 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SpanIter::next (cognitive 25) yazi-shim/src/ratatui/span.rs:52— SpanIter::next has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (4 pts), boolean chains 3, match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Sixel::encode (cognitive 24) yazi-adapter/src/drivers/sixel.rs:49— Sixel::encode has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 3 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
yazi_tui::backend::write_modifier_diff (cognitive 24) yazi-tui/src/backend.rs:119— yazi_tui::backend::write_modifier_diff has cognitive complexity 24 (threshold 15). Drivers by points: if/else 18 (20 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Refresher::handle (cognitive 21) yazi-watcher/src/refresher.rs:43— Refresher::handle has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (10 pts), match/switch 4 (7 pts), boolean chains 2, loops 1 (2 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.
Style::add_methods (cognitive 20) yazi-binding/src/style/style.rs:44— Style::add_methods has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18, match/switch 2. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Session::make (cognitive 20) yazi-sftp/src/session.rs:23— Session::make has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (5 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 8). Of this number, 17 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Line::add_methods (cognitive 19) yazi-binding/src/elements/line.rs:123— Line::add_methods has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), match/switch 4 (5 pts), loops 2, boolean chains 1 (nesting depth added 2). Of this number, 15 points are the body's own statements and 4 belong to one function item inside it that branches. 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.
Client::serve (cognitive 19) yazi-dds/src/client.rs:34— Client::serve has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), match/switch 2 (5 pts), 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.
Cd::cd_interactive (cognitive 18) yazi-actor/src/mgr/cd.rs:65— Cd::cd_interactive has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Remover::remove (cognitive 18) yazi-fs/src/remover/unix.rs:9— Remover::remove has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), match/switch 2 (4 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Virtual::changed (cognitive 18) yazi-watcher/src/virtual/virtual.rs:33— Virtual::changed has cognitive complexity 18 (threshold 15). Drivers by points: if/else 2 (6 pts), match/switch 2 (6 pts), loops 3 (5 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.
Copy::act (cognitive 17) yazi-actor/src/mgr/copy.rs:18— Copy::act has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, match/switch 1 (2 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.
Bar::render (cognitive 17) yazi-binding/src/elements/bar.rs:41— Bar::render has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, loops 4 (8 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Child::add_methods (cognitive 17) yazi-binding/src/process/child.rs:88— Child::add_methods has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 14, if/else 3. Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
Data::from_lua (cognitive 17) yazi-shared/src/data/lua.rs:10— Data::from_lua has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), match/switch 3 (5 pts), loops 2 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Peek::act (cognitive 16) yazi-actor/src/mgr/peek.rs:16— Peek::act 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.
Engine::remove_dir_clean (cognitive 16) yazi-fs/src/engine/traits.rs:124— Engine::remove_dir_clean has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Attrs::serialize (cognitive 16) yazi-sftp/src/fs/attrs.rs:42— Attrs::serialize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 4, loops 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Local::changed (cognitive 16) yazi-watcher/src/local/local.rs:88— Local::changed has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (6 pts), match/switch 2 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodTooLong: Spark.into_lua yazi-parser/src/spark/spark.rs:206— MethodTooLong — into_lua runs 136 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 36 over it, 1.36× 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.
TooManyFunctions: yazi_vfs::engine::engine yazi-vfs/src/engine/engine.rs:8— TooManyFunctions — 31 free functions. The bar is 30 free functions; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change-coupling hub: kgp.rs → iip.rs, kgp_old.rs, sixel.rs yazi-adapter/src/drivers/kgp.rs— `yazi-adapter/src/drivers/kgp.rs` changes together with 3 other files — `yazi-adapter/src/drivers/iip.rs`, `yazi-adapter/src/drivers/kgp_old.rs`, `yazi-adapter/src/drivers/sixel.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Near-duplicate member pair (41 shared lines) yazi-adapter/src/drivers/kgp.rs:352— yazi-adapter/src/drivers/kgp.rs:352-404 | yazi-adapter/src/drivers/kgp_old.rs:53-104 — These two members are variants of one another: 41 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (7 members, 50+ identical tokens) yazi-config/src/keymap/chords.rs:74— yazi-config/src/keymap/chords.rs:74-115 | yazi-config/src/open/open_rules.rs:93-123 | yazi-config/src/opener/opener_rules_arc.rs:35-60 | yazi-config/src/plugin/fetchers.rs:114-144 | yazi-config/src/plugin/preloaders.rs:118-148 | yazi-config/src/plugin/previewers.rs:93-123 | yazi-config/src/plugin/spotters.rs:95-125 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) yazi-scheduler/src/worker.rs:100— yazi-scheduler/src/worker.rs:100-112 | yazi-scheduler/src/worker.rs:135-147 | yazi-scheduler/src/worker.rs:156-168 | yazi-scheduler/src/worker.rs:177-189 | yazi-scheduler/src/worker.rs:198-218 | yazi-scheduler/src/worker.rs:224-236 — These 6 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 6 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 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) yazi-scheduler/src/file/out.rs:24— yazi-scheduler/src/file/out.rs:24-47 | yazi-scheduler/src/file/out.rs:99-126 | yazi-scheduler/src/file/out.rs:231-253 | yazi-scheduler/src/file/out.rs:365-388 | yazi-scheduler/src/file/out.rs:436-459 — 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.
Duplicated block (18 lines × 2) yazi-shared/src/shell/unix.rs:89— yazi-shared/src/shell/unix.rs:89-106 | yazi-shared/src/shell/unix.rs:118-135 — 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 (17 lines × 4) yazi-scheduler/src/file/out.rs:26— yazi-scheduler/src/file/out.rs:26-42 | yazi-scheduler/src/file/out.rs:101-117 | yazi-scheduler/src/file/out.rs:367-383 | yazi-scheduler/src/file/out.rs:438-454 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16 lines × 2) yazi-fs/src/engine/local/calculator.rs:76— yazi-fs/src/engine/local/calculator.rs:76-91 | yazi-vfs/src/engine/calculator.rs:54-69 — 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 (14 lines × 4) yazi-scheduler/src/file/out.rs:34— yazi-scheduler/src/file/out.rs:34-47 | yazi-scheduler/src/file/out.rs:240-253 | yazi-scheduler/src/file/out.rs:375-388 | yazi-scheduler/src/file/out.rs:446-459 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 4) yazi-scheduler/src/file/out.rs:65— yazi-scheduler/src/file/out.rs:65-77 | yazi-scheduler/src/file/out.rs:144-156 | yazi-scheduler/src/file/out.rs:406-418 | yazi-scheduler/src/file/out.rs:477-489 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8–10 lines × 2) yazi-fs/src/trash/freedesktop/trash.rs:81— yazi-fs/src/trash/freedesktop/trash.rs:81-90 | yazi-fs/src/trash/macos/trash.rs:82-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 7) yazi-config/src/keymap/chords.rs:83— yazi-config/src/keymap/chords.rs:83-91 | yazi-config/src/open/open_rules.rs:102-110 | yazi-config/src/opener/opener_rules_arc.rs:44-52 | yazi-config/src/plugin/fetchers.rs:123-131 | yazi-config/src/plugin/preloaders.rs:127-135 | yazi-config/src/plugin/previewers.rs:102-110 | yazi-config/src/plugin/spotters.rs:104-112 — before extracting anything, compare `yazi-config/src/plugin/previewers.rs` and `yazi-config/src/plugin/spotters.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (5–7 lines × 2) yazi-tty/src/sequence/dnd.rs:95— yazi-tty/src/sequence/dnd.rs:95-99 | yazi-tty/src/sequence/dnd.rs:123-129 — 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 × 6) yazi-scheduler/src/worker.rs:102— yazi-scheduler/src/worker.rs:102-107 | yazi-scheduler/src/worker.rs:137-142 | yazi-scheduler/src/worker.rs:158-163 | yazi-scheduler/src/worker.rs:179-184 | yazi-scheduler/src/worker.rs:200-205 | yazi-scheduler/src/worker.rs:226-231 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (17 lines × 2) yazi-config/src/plugin/previewers.rs:43— yazi-config/src/plugin/previewers.rs:43-59 | yazi-config/src/plugin/spotters.rs:45-61 — before extracting anything, compare `yazi-config/src/plugin/previewers.rs` and `yazi-config/src/plugin/spotters.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 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 (25 lines × 2) yazi-config/src/plugin/fetcher_arc.rs:21— yazi-config/src/plugin/fetcher_arc.rs:21-45 | yazi-config/src/plugin/preloader_arc.rs:21-45 — 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 (29 lines × 2) yazi-config/src/plugin/previewer_arc.rs:16— yazi-config/src/plugin/previewer_arc.rs:16-44 | yazi-config/src/plugin/spotter_arc.rs:16-44 — 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 × 21) yazi-parser/src/app/deprecate.rs:12— yazi-parser/src/app/deprecate.rs:12-20 | yazi-parser/src/app/lua.rs:15-23 | yazi-parser/src/app/passthrough.rs:11-19 | yazi-parser/src/help/toggle.rs:12-24 | yazi-parser/src/input/recall.rs:13-21 | yazi-parser/src/mgr/bulk_exit.rs:14-22 | yazi-parser/src/mgr/create.rs:16-24 | yazi-parser/src/mgr/hardlink.rs:14-22 | yazi-parser/src/mgr/link.rs:16-24 | yazi-parser/src/mgr/paste.rs:14-22 | yazi-parser/src/mgr/seek.rs:12-20 | yazi-parser/src/mgr/tab_close.rs:12-24 | yazi-parser/src/mgr/tab_switch.rs:14-22 | yazi-parser/src/mgr/update_mimes.rs:13-21 | yazi-parser/src/mgr/visual_arrow.rs:12-20 | yazi-parser/src/mgr/visual_mode.rs:12-20 | yazi-parser/src/mgr/yank.rs:12-20 | yazi-parser/src/notify/tick.rs:17-25 | yazi-parser/src/tasks/update_succeed.rs:15-23 | yazi-widgets/src/input/parser/backward.rs:14-22 | yazi-widgets/src/input/parser/forward.rs:17-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 21 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 21 times.
Duplicated block (15 lines × 3) yazi-parser/src/cmp/close.rs:10— yazi-parser/src/cmp/close.rs:10-24 | yazi-parser/src/confirm/close.rs:10-24 | yazi-parser/src/pick/close.rs:10-24 — 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 × 3) yazi-parser/src/mgr/filter.rs:11— yazi-parser/src/mgr/filter.rs:11-23 | yazi-parser/src/mgr/find_do.rs:11-23 | yazi-parser/src/mgr/open.rs:11-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (5 lines × 6) yazi-sftp/src/requests/open_dir.rs:15— yazi-sftp/src/requests/open_dir.rs:15-19 | yazi-sftp/src/requests/readlink.rs:15-19 | yazi-sftp/src/requests/realpath.rs:15-19 | yazi-sftp/src/requests/remove.rs:15-19 | yazi-sftp/src/requests/rmdir.rs:15-19 | yazi-sftp/src/requests/stat.rs:15-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 6 call sites, so a change lands once.
Duplicated block (7 lines × 5) yazi-config/src/keymap/chords.rs:42— yazi-config/src/keymap/chords.rs:42-48 | yazi-config/src/open/open_rules.rs:61-67 | yazi-config/src/opener/opener_rules.rs:39-45 | yazi-config/src/plugin/previewers.rs:61-67 | yazi-config/src/plugin/spotters.rs:63-69 — before extracting anything, compare `yazi-config/src/plugin/previewers.rs` and `yazi-config/src/plugin/spotters.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 5) yazi-config/src/open/open_rule_matcher.rs:27— yazi-config/src/open/open_rule_matcher.rs:27-35 | yazi-config/src/plugin/fetcher.rs:71-79 | yazi-config/src/plugin/preloader.rs:58-66 | yazi-config/src/plugin/previewer.rs:58-66 | yazi-config/src/plugin/spotter.rs:58-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (6 lines × 5) yazi-scheduler/src/fetch/in.rs:19— yazi-scheduler/src/fetch/in.rs:19-24 | yazi-scheduler/src/fetch/in.rs:34-39 | yazi-scheduler/src/fetch/in.rs:41-46 | yazi-scheduler/src/plugin/in.rs:21-26 | yazi-scheduler/src/preload/in.rs:18-23 — there are 5 copies across 3 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (7 lines × 4) yazi-vfs/src/engine/dir_entry.rs:13— yazi-vfs/src/engine/dir_entry.rs:13-19 | yazi-vfs/src/engine/dir_entry.rs:21-27 | yazi-vfs/src/engine/dir_entry.rs:29-35 | yazi-vfs/src/engine/engines.rs:33-39 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart.
Duplicated predicate yazi-fs/src/trash/freedesktop/trash.rs:85— `!latest.hits(current) || latest.extra.link_to() != current.extra.link_to() || latest.extra.backing() != current.extra.backing()` appears character-identically in 2 files — yazi-fs/src/trash/freedesktop/trash.rs, yazi-fs/src/trash/macos/trash.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 yazi-fs/src/trash/macos/ds_store.rs:37— `!rel.is_relative() || rel.has_parent_component()` appears character-identically in 2 files — yazi-fs/src/trash/macos/ds_store.rs, yazi-fs/src/trash/trash_id.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 yazi-runner/src/entry/entry.rs:34— `scope.is_cancelled() && dbg.source().what != "C"` appears character-identically in 5 files — yazi-runner/src/entry/entry.rs, yazi-runner/src/fetcher/fetcher.rs, yazi-runner/src/preloader/preloader.rs, yazi-runner/src/previewer/previewer.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 yazi-scheduler/src/file/progress.rs:126— `self.cleaned.is_failed() || self.state == Some(false)` appears character-identically in 2 files — yazi-scheduler/src/file/progress.rs, yazi-scheduler/src/preload/progress.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.
Orphaned file yazi-shared/src/translit/table.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file yazi-adapter/src/icc.rs:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 170 significant file(s) lose their only recent owner: yazi-shared/src/url/buf.rs, yazi-scheduler/src/file/file.rs, yazi-vfs/src/engine/lua/file.rs, yazi-shared/src/url/url.rs, yazi-scheduler/src/worker.rs, yazi-scheduler/src/file/out.rs, yazi-term/src/parser/csi.rs, yazi-shared/src/loc/buf.rs (+162 more). Pair on, review, or document these before any departure.
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 — 3 of 31 project(s) overshoot their size bounds, lowering Project Cohesion to 8.4/10. The most over is `yazi-fs` (7640 LoC, 76 module-visible types across 17 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.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 2 of 262 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 262 of the 1350 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: yazi-shared/src/translit/table.rs, yazi-adapter/src/icc.rs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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 19/21 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `yazi-build`, `yazi-cli`.
Silent fallback default on Err yazi-fs/src/mounts/windows.rs:102— `volume_paths` turns every `Err` into `vec![]` — 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: 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.2.0"` requirement declared in yazi-watcher/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: ordered-float — `ordered-float` is locked at 5.5.0 but 5.5.1 is the current stable release on crates.io, and it already satisfies the `"5.5.0"` requirement declared in yazi-scheduler/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ordered-float` and commit the updated REDACTED.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1750e-2c83-7f85-9eb6-b035a0e6a20f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 61 · Warnings: 256 · Recommendations: 17 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 25-10-2026 @ 21:53 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.