Public report of gitui-org/gitui, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 05:33 UTC · Survey ID cd_3301ce28c7f64ff89764a2c6b8593450
gitui-org/gitui
Measured 14 November 2026, 05:31 UTC, at code version d7214ec
CAI scoreStrong
CriticalWeakAdequateStrongExemplary
Down 5 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: 43,639 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Security and Compliance, 53
Findings by how serious they are
49 critical400 serious110 minor
19 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 05:31 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
42of 42 dimensions measured by tools.
523of 559 findings point to an exact file and line, so you can open each one in the code. The other 36 concern the repository as a whole, such as missing documentation.
42dimensions across 6 lenses, read from 43,639 lines of product code in 7 projects.
gitui-org/gitui meets our standard for a preview release, though it has pipeline tools referenced by a changeable name. It scores 66 out of 100 and is rated Strong, and all 49 of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Security and Compliance, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 4 points. Fixing the two pipeline jobs with more access than they need would lift Security and Compliance itself, worth about 2 points. Raising Security and Compliance to 68 would lift the score to about 73.
Thirty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three pipeline steps run downloads nobody checks, and three secrets can leak from the build pipeline. Pinning each tool to an exact version, checking each download against a checksum and limiting each secret to its own step would close these risks. Correcting the flagged pipeline settings would fix the two weaknesses in the build pipeline's configuration, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once.
The product code is 43,639 lines, about €53,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.
If Security and Compliance rose from 53 to 68, the lowest score rated Strong, the score would rise from 66 to about 73.
Code composition: what the lines of code are
Product code 100%Tests 0%
New since the last survey: 162 findings
These 162 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Edited copy of a member (87 corresponding lines) REDACTED
Code Duplication · Edited copy of a member (52 corresponding lines) asyncgit/src/sync/sign.rs
Code Duplication · Edited copy of a member (54 corresponding lines) asyncgit/src/blame.rs
Code Duplication · Edited copies of one member (3 members, 46+ corresponding lines) asyncgit/src/pull.rs
Code Duplication · Edited copy of a member (30 corresponding lines) src/popups/branchlist.rs
Code Duplication · Edited copies of one member (3 members, 37+ corresponding lines) src/popups/branchlist.rs
Code Duplication · Edited copy of a member (36 corresponding lines) src/ui/scrollbar.rs
Code Duplication · Edited copy of a member (37 corresponding lines) asyncgit/src/sync/branch/merge_commit.rs
Code Duplication · Edited copy of a member (37 corresponding lines) asyncgit/src/revlog.rs
Code Duplication · Edited copy of a member (40 corresponding lines) filetreelist/src/filetreeitems.rs
Code Duplication · Edited copy of a member (29 corresponding lines) filetreelist/src/filetreeitems.rs
Code Duplication · Edited copies of one member (3 members, 43+ corresponding lines) src/popups/commit.rs
Code Duplication · Edited copy of a member (33 corresponding lines) src/popups/create_branch.rs
Code Duplication · Edited copies of one member (3 members, 43+ corresponding lines) REDACTED
Code Duplication · Edited copy of a member (30 corresponding lines) REDACTED
Code Duplication · Edited copies of one member (3 members, 31+ corresponding lines) src/popups/compare_commits.rs
Code Duplication · Edited copy of a member (32 corresponding lines) src/popups/compare_commits.rs
Code Duplication · Edited copies of one member (3 members, 27+ corresponding lines) src/popups/checkout_option.rs
Code Duplication · Edited copies of one member (3 members, 29+ corresponding lines) src/popups/branchlist.rs
Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) asyncgit/src/sync/cred.rs
Code Duplication · Edited copy of a member (24 corresponding lines) asyncgit/src/sync/rebase.rs
Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) src/popups/branchlist.rs
Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) src/popups/checkout_option.rs
Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) src/popups/rename_branch.rs
Code Duplication · Edited copy of a member (26 corresponding lines) filetreelist/src/filetreeitems.rs
Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) src/popups/fetch.rs
Code Duplication · Edited copy of a member (20 corresponding lines) src/popups/fuzzy_find.rs
Code Duplication · Edited copy of a member (17 corresponding lines) src/popups/fetch.rs
Code Duplication · Edited copy of a member (11 corresponding lines) asyncgit/src/sync/branch/mod.rs
Code Duplication · Edited copy of a member (16 corresponding lines) src/components/diff.rs
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) src/popups/pull.rs
Code Duplication · Edited copy of a member (15 corresponding lines) src/popups/compare_commits.rs
Code Duplication · Edited copy of a member (22 corresponding lines) src/popups/goto_line.rs
Code Duplication · Edited copy of a member (15 corresponding lines) src/popups/push.rs
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) src/popups/create_remote.rs
Code Duplication · Edited copy of a member (16 corresponding lines) src/popups/rename_remote.rs
Code Duplication · Edited copies of one member (5 members, 14+ corresponding lines) asyncgit/src/branches.rs
Code Duplication · Edited copy of a member (22 corresponding lines) filetreelist/src/filetreeitems.rs
Code Duplication · Edited copy of a member (15 corresponding lines) src/popups/branchlist.rs
Code Duplication · Edited copy of a member (19 corresponding lines) src/components/cred.rs
Code Duplication · Edited copy of a member (12 corresponding lines) asyncgit/src/sync/commits_info.rs
Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) src/popups/create_branch.rs
Code Duplication · Edited copy of a member (15 corresponding lines) src/popups/branchlist.rs
Code Duplication · Edited copy of a member (19 corresponding lines) src/components/utils/scroll_horizontal.rs
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) asyncgit/src/sync/cred.rs
Code Duplication · Edited copy of a member (14 corresponding lines) src/popups/confirm.rs
Code Duplication · Edited copy of a member (11 corresponding lines) src/popups/checkout_option.rs
Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) src/popups/compare_commits.rs
Code Duplication · Edited copy of a member (10 corresponding lines) filetreelist/src/filetree.rs
Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) asyncgit/src/blame.rs
Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) src/popups/create_branch.rs
Code Duplication · Edited copy of a member (13 corresponding lines) src/strings.rs
Code Duplication · Edited copy of a member (9 corresponding lines) src/ui/scrolllist.rs
Code Duplication · Edited copy of a member (11 corresponding lines) asyncgit/src/sync/commit_revert.rs
Code Duplication · Edited copy of a member (11 corresponding lines) src/popups/push.rs
Code Duplication · Edited copy of a member (6 corresponding lines) src/keys/symbols.rs
Code Duplication · Edited copy of a member (5 corresponding lines) asyncgit/src/blame.rs
Code Duplication · Edited copy of a member (4 corresponding lines) asyncgit/src/pull.rs
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 16 findings
These 16 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one.
Test Reliability · Flaky test: gitui::bin/gitui.gitui::tests::gitui_starts
Rebuild cost: about €53,000 · Estimate
Cost to rebuild
€17,000 to €88,000, for 291 to 923 hours of work, about 0.4 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.9 at a score of 66. 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: 43,639 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 4 points · Low effort · ADR Quality
2
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED.
Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €53,000 to build again, about 0.4 person-years of work. Its weakest lens is Security and Compliance, at 53 (Adequate). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
158 modules, with 531 dependencies between them. 4 loops run through 56 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 118 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.
asyncgit.sync.commits_info uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break asyncgit.sync.commits_info, while a change to asyncgit.sync.commits_info can't break asyncgit.sync.repository.
Position
Below the diagonal: asyncgit.sync.commits_info uses a module listed above it, which is the healthy direction.
asyncgit.sync.cred uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break asyncgit.sync.cred, while a change to asyncgit.sync.cred can't break asyncgit.sync.repository.
Position
Below the diagonal: asyncgit.sync.cred uses a module listed above it, which is the healthy direction.
asyncgit.sync.status uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break asyncgit.sync.status, while a change to asyncgit.sync.status can't break asyncgit.sync.repository.
Position
Below the diagonal: asyncgit.sync.status uses a module listed above it, which is the healthy direction.
gitui.components uses gitui.components.command, so a change to gitui.components.command can break gitui.components, while a change to gitui.components can't break gitui.components.command.
Position
Below the diagonal: gitui.components uses a module listed above it, which is the healthy direction.
asyncgit.sync.diff uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break asyncgit.sync.diff, while a change to asyncgit.sync.diff can't break asyncgit.sync.repository.
Position
Below the diagonal: asyncgit.sync.diff uses a module listed above it, which is the healthy direction.
asyncgit.sync.diff uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break asyncgit.sync.diff, while a change to asyncgit.sync.diff can't break asyncgit.sync.commits_info.
Position
Below the diagonal: asyncgit.sync.diff uses a module listed above it, which is the healthy direction.
asyncgit.sync.remotes.push uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break asyncgit.sync.remotes.push, while a change to asyncgit.sync.remotes.push can't break asyncgit.sync.repository.
Position
Below the diagonal: asyncgit.sync.remotes.push uses a module listed above it, which is the healthy direction.
asyncgit.sync.remotes.push uses asyncgit.sync.cred, so a change to asyncgit.sync.cred can break asyncgit.sync.remotes.push, while a change to asyncgit.sync.remotes.push can't break asyncgit.sync.cred.
Position
Below the diagonal: asyncgit.sync.remotes.push uses a module listed above it, which is the healthy direction.
gitui.components.commitlist uses gitui.components.command, so a change to gitui.components.command can break gitui.components.commitlist, while a change to gitui.components.commitlist can't break gitui.components.command.
Position
Below the diagonal: gitui.components.commitlist uses a module listed above it, which is the healthy direction.
gitui.components.commitlist uses gitui.queue, so a change to gitui.queue can break gitui.components.commitlist, while a change to gitui.components.commitlist can't break gitui.queue.
Position
Below the diagonal: gitui.components.commitlist uses a module listed above it, which is the healthy direction.
gitui.components.commitlist uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.components.commitlist, while a change to gitui.components.commitlist can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.components.commitlist uses a module listed above it, which is the healthy direction.
gitui.components.commitlist uses gitui.components, so a change to gitui.components can break gitui.components.commitlist, while a change to gitui.components.commitlist can't break gitui.components.
Position
Below the diagonal: gitui.components.commitlist uses a module listed above it, which is the healthy direction.
12→39 gitui.components.commitlist uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.commitlist uses a type in gitui.app.
gitui.components.commitlist uses gitui.app, so a change to gitui.app can break gitui.components.commitlist, while a change to gitui.components.commitlist can't break gitui.app.
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.
gitui.components.status_tree uses gitui.components.command, so a change to gitui.components.command can break gitui.components.status_tree, while a change to gitui.components.status_tree can't break gitui.components.command.
Position
Below the diagonal: gitui.components.status_tree uses a module listed above it, which is the healthy direction.
gitui.components.status_tree uses gitui.queue, so a change to gitui.queue can break gitui.components.status_tree, while a change to gitui.components.status_tree can't break gitui.queue.
Position
Below the diagonal: gitui.components.status_tree uses a module listed above it, which is the healthy direction.
gitui.components.status_tree uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.components.status_tree, while a change to gitui.components.status_tree can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.components.status_tree uses a module listed above it, which is the healthy direction.
gitui.components.status_tree uses asyncgit.sync.status, so a change to asyncgit.sync.status can break gitui.components.status_tree, while a change to gitui.components.status_tree can't break asyncgit.sync.status.
Position
Below the diagonal: gitui.components.status_tree uses a module listed above it, which is the healthy direction.
gitui.components.status_tree uses gitui.components, so a change to gitui.components can break gitui.components.status_tree, while a change to gitui.components.status_tree can't break gitui.components.
Position
Below the diagonal: gitui.components.status_tree uses a module listed above it, which is the healthy direction.
13→39 gitui.components.status_tree uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.status_tree uses a type in gitui.app.
gitui.components.status_tree uses gitui.app, so a change to gitui.app can break gitui.components.status_tree, while a change to gitui.components.status_tree can't break gitui.app.
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.
gitui.components.syntax_text uses asyncgit.asyncjob, so a change to asyncgit.asyncjob can break gitui.components.syntax_text, while a change to gitui.components.syntax_text can't break asyncgit.asyncjob.
Position
Below the diagonal: gitui.components.syntax_text uses a module listed above it, which is the healthy direction.
gitui.components.syntax_text uses gitui.components.command, so a change to gitui.components.command can break gitui.components.syntax_text, while a change to gitui.components.syntax_text can't break gitui.components.command.
Position
Below the diagonal: gitui.components.syntax_text uses a module listed above it, which is the healthy direction.
gitui.components.syntax_text uses gitui.components, so a change to gitui.components can break gitui.components.syntax_text, while a change to gitui.components.syntax_text can't break gitui.components.
Position
Below the diagonal: gitui.components.syntax_text uses a module listed above it, which is the healthy direction.
14→39 gitui.components.syntax_text uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.syntax_text uses a type in gitui.app.
gitui.components.syntax_text uses gitui.app, so a change to gitui.app can break gitui.components.syntax_text, while a change to gitui.components.syntax_text can't break gitui.app.
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.
14→40 gitui.components.syntax_text uses gituipart of a loop✕
Connections
1 pair of types, where a type in gitui.components.syntax_text uses a type in gitui.
gitui.components.syntax_text uses gitui, so a change to gitui can break gitui.components.syntax_text, while a change to gitui.components.syntax_text can't break gitui.
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.
gitui.components.textinput uses gitui.components.command, so a change to gitui.components.command can break gitui.components.textinput, while a change to gitui.components.textinput can't break gitui.components.command.
Position
Below the diagonal: gitui.components.textinput uses a module listed above it, which is the healthy direction.
gitui.components.textinput uses gitui.components, so a change to gitui.components can break gitui.components.textinput, while a change to gitui.components.textinput can't break gitui.components.
Position
Below the diagonal: gitui.components.textinput uses a module listed above it, which is the healthy direction.
15→39 gitui.components.textinput uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.textinput uses a type in gitui.app.
gitui.components.textinput uses gitui.app, so a change to gitui.app can break gitui.components.textinput, while a change to gitui.components.textinput can't break gitui.app.
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.
gitui.components.utils.scroll_vertical uses gitui.components, so a change to gitui.components can break gitui.components.utils.scroll_vertical, while a change to gitui.components.utils.scroll_vertical can't break gitui.components.
Position
Below the diagonal: gitui.components.utils.scroll_vertical uses a module listed above it, which is the healthy direction.
gitui.popups.blame_file uses asyncgit, so a change to asyncgit can break gitui.popups.blame_file, while a change to gitui.popups.blame_file can't break asyncgit.
Position
Below the diagonal: gitui.popups.blame_file uses a module listed above it, which is the healthy direction.
gitui.popups.blame_file uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.blame_file, while a change to gitui.popups.blame_file can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.blame_file uses a module listed above it, which is the healthy direction.
gitui.popups.blame_file uses gitui.queue, so a change to gitui.queue can break gitui.popups.blame_file, while a change to gitui.popups.blame_file can't break gitui.queue.
Position
Below the diagonal: gitui.popups.blame_file uses a module listed above it, which is the healthy direction.
gitui.popups.blame_file uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.popups.blame_file, while a change to gitui.popups.blame_file can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.popups.blame_file uses a module listed above it, which is the healthy direction.
gitui.popups.blame_file uses gitui.components, so a change to gitui.components can break gitui.popups.blame_file, while a change to gitui.popups.blame_file can't break gitui.components.
Position
Below the diagonal: gitui.popups.blame_file uses a module listed above it, which is the healthy direction.
17→39 gitui.popups.blame_file uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.blame_file uses a type in gitui.app.
gitui.popups.blame_file uses gitui.app, so a change to gitui.app can break gitui.popups.blame_file, while a change to gitui.popups.blame_file can't break gitui.app.
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.
17→40 gitui.popups.blame_file uses gituipart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.blame_file uses a type in gitui.
gitui.popups.blame_file uses gitui, so a change to gitui can break gitui.popups.blame_file, while a change to gitui.popups.blame_file can't break gitui.
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.
gitui.popups.checkout_option uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break gitui.popups.checkout_option, while a change to gitui.popups.checkout_option can't break asyncgit.sync.repository.
Position
Below the diagonal: gitui.popups.checkout_option uses a module listed above it, which is the healthy direction.
gitui.popups.checkout_option uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.checkout_option, while a change to gitui.popups.checkout_option can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.checkout_option uses a module listed above it, which is the healthy direction.
gitui.popups.checkout_option uses gitui.queue, so a change to gitui.queue can break gitui.popups.checkout_option, while a change to gitui.popups.checkout_option can't break gitui.queue.
Position
Below the diagonal: gitui.popups.checkout_option uses a module listed above it, which is the healthy direction.
gitui.popups.checkout_option uses gitui.components, so a change to gitui.components can break gitui.popups.checkout_option, while a change to gitui.popups.checkout_option can't break gitui.components.
Position
Below the diagonal: gitui.popups.checkout_option uses a module listed above it, which is the healthy direction.
18→39 gitui.popups.checkout_option uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.checkout_option uses a type in gitui.app.
gitui.popups.checkout_option uses gitui.app, so a change to gitui.app can break gitui.popups.checkout_option, while a change to gitui.popups.checkout_option can't break gitui.app.
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.
gitui.popups.reset uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break gitui.popups.reset, while a change to gitui.popups.reset can't break asyncgit.sync.repository.
Position
Below the diagonal: gitui.popups.reset uses a module listed above it, which is the healthy direction.
gitui.popups.reset uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.reset, while a change to gitui.popups.reset can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.reset uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.popups.reset uses a type in gitui.queue.
The types involved
gitui.popups.reset.ResetPopup → gitui.queue.Queue
Direction
gitui.popups.reset uses gitui.queue, so a change to gitui.queue can break gitui.popups.reset, while a change to gitui.popups.reset can't break gitui.queue.
Position
Below the diagonal: gitui.popups.reset uses a module listed above it, which is the healthy direction.
gitui.popups.reset uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.popups.reset, while a change to gitui.popups.reset can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.popups.reset uses a module listed above it, which is the healthy direction.
gitui.popups.reset uses gitui.components, so a change to gitui.components can break gitui.popups.reset, while a change to gitui.popups.reset can't break gitui.components.
Position
Below the diagonal: gitui.popups.reset uses a module listed above it, which is the healthy direction.
19→39 gitui.popups.reset uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.reset uses a type in gitui.app.
gitui.popups.taglist uses asyncgit.asyncjob, so a change to asyncgit.asyncjob can break gitui.popups.taglist, while a change to gitui.popups.taglist can't break asyncgit.asyncjob.
Position
Below the diagonal: gitui.popups.taglist uses a module listed above it, which is the healthy direction.
gitui.popups.taglist uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.taglist, while a change to gitui.popups.taglist can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.taglist uses a module listed above it, which is the healthy direction.
gitui.popups.taglist uses gitui.queue, so a change to gitui.queue can break gitui.popups.taglist, while a change to gitui.popups.taglist can't break gitui.queue.
Position
Below the diagonal: gitui.popups.taglist uses a module listed above it, which is the healthy direction.
gitui.popups.taglist uses asyncgit.sync.cred, so a change to asyncgit.sync.cred can break gitui.popups.taglist, while a change to gitui.popups.taglist can't break asyncgit.sync.cred.
Position
Below the diagonal: gitui.popups.taglist uses a module listed above it, which is the healthy direction.
gitui.popups.taglist uses gitui.components, so a change to gitui.components can break gitui.popups.taglist, while a change to gitui.popups.taglist can't break gitui.components.
Position
Below the diagonal: gitui.popups.taglist uses a module listed above it, which is the healthy direction.
20→39 gitui.popups.taglist uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.taglist uses a type in gitui.app.
gitui.popups.taglist uses gitui.app, so a change to gitui.app can break gitui.popups.taglist, while a change to gitui.popups.taglist can't break gitui.app.
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.
20→40 gitui.popups.taglist uses gituipart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.taglist uses a type in gitui.
gitui.components.commit_details.details uses gitui.components.command, so a change to gitui.components.command can break gitui.components.commit_details.details, while a change to gitui.components.commit_details.details can't break gitui.components.command.
Position
Below the diagonal: gitui.components.commit_details.details uses a module listed above it, which is the healthy direction.
gitui.components.commit_details.details uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.components.commit_details.details, while a change to gitui.components.commit_details.details can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.components.commit_details.details uses a module listed above it, which is the healthy direction.
gitui.components.commit_details.details uses gitui.components, so a change to gitui.components can break gitui.components.commit_details.details, while a change to gitui.components.commit_details.details can't break gitui.components.
Position
Below the diagonal: gitui.components.commit_details.details uses a module listed above it, which is the healthy direction.
gitui.components.commit_details.details uses gitui.components.utils.scroll_vertical, so a change to gitui.components.utils.scroll_vertical can break gitui.components.commit_details.details, while a change to gitui.components.commit_details.details can't break gitui.components.utils.scroll_vertical.
Position
Below the diagonal: gitui.components.commit_details.details uses a module listed above it, which is the healthy direction.
21→39 gitui.components.commit_details.details uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.commit_details.details uses a type in gitui.app.
gitui.components.commit_details.details uses gitui.app, so a change to gitui.app can break gitui.components.commit_details.details, while a change to gitui.components.commit_details.details can't break gitui.app.
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.
gitui.components.cred uses gitui.components.command, so a change to gitui.components.command can break gitui.components.cred, while a change to gitui.components.cred can't break gitui.components.command.
Position
Below the diagonal: gitui.components.cred uses a module listed above it, which is the healthy direction.
gitui.components.cred uses asyncgit.sync.cred, so a change to asyncgit.sync.cred can break gitui.components.cred, while a change to gitui.components.cred can't break asyncgit.sync.cred.
Position
Below the diagonal: gitui.components.cred uses a module listed above it, which is the healthy direction.
gitui.components.cred uses gitui.components, so a change to gitui.components can break gitui.components.cred, while a change to gitui.components.cred can't break gitui.components.
Position
Below the diagonal: gitui.components.cred uses a module listed above it, which is the healthy direction.
gitui.components.cred uses gitui.components.textinput, so a change to gitui.components.textinput can break gitui.components.cred, while a change to gitui.components.cred can't break gitui.components.textinput.
Position
Below the diagonal: gitui.components.cred uses a module listed above it, which is the healthy direction.
22→39 gitui.components.cred uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.cred uses a type in gitui.app.
gitui.components.cred uses gitui.app, so a change to gitui.app can break gitui.components.cred, while a change to gitui.components.cred can't break gitui.app.
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.
gitui.components.diff uses gitui.components.command, so a change to gitui.components.command can break gitui.components.diff, while a change to gitui.components.diff can't break gitui.components.command.
Position
Below the diagonal: gitui.components.diff uses a module listed above it, which is the healthy direction.
gitui.components.diff uses gitui.queue, so a change to gitui.queue can break gitui.components.diff, while a change to gitui.components.diff can't break gitui.queue.
Position
Below the diagonal: gitui.components.diff uses a module listed above it, which is the healthy direction.
gitui.components.diff uses gitui.components, so a change to gitui.components can break gitui.components.diff, while a change to gitui.components.diff can't break gitui.components.
Position
Below the diagonal: gitui.components.diff uses a module listed above it, which is the healthy direction.
gitui.components.diff uses asyncgit.sync.diff, so a change to asyncgit.sync.diff can break gitui.components.diff, while a change to gitui.components.diff can't break asyncgit.sync.diff.
Position
Below the diagonal: gitui.components.diff uses a module listed above it, which is the healthy direction.
gitui.components.diff uses gitui.components.utils.scroll_vertical, so a change to gitui.components.utils.scroll_vertical can break gitui.components.diff, while a change to gitui.components.diff can't break gitui.components.utils.scroll_vertical.
Position
Below the diagonal: gitui.components.diff uses a module listed above it, which is the healthy direction.
23→39 gitui.components.diff uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.diff uses a type in gitui.app.
gitui.components.diff uses gitui.app, so a change to gitui.app can break gitui.components.diff, while a change to gitui.components.diff can't break gitui.app.
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.
gitui.components.revision_files uses asyncgit.asyncjob, so a change to asyncgit.asyncjob can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break asyncgit.asyncjob.
Position
Below the diagonal: gitui.components.revision_files uses a module listed above it, which is the healthy direction.
gitui.components.revision_files uses gitui.components.command, so a change to gitui.components.command can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break gitui.components.command.
Position
Below the diagonal: gitui.components.revision_files uses a module listed above it, which is the healthy direction.
gitui.components.revision_files uses gitui.queue, so a change to gitui.queue can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break gitui.queue.
Position
Below the diagonal: gitui.components.revision_files uses a module listed above it, which is the healthy direction.
gitui.components.revision_files uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.components.revision_files uses a module listed above it, which is the healthy direction.
gitui.components.revision_files uses gitui.components, so a change to gitui.components can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break gitui.components.
Position
Below the diagonal: gitui.components.revision_files uses a module listed above it, which is the healthy direction.
gitui.components.revision_files uses gitui.components.syntax_text, so a change to gitui.components.syntax_text can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break gitui.components.syntax_text.
Position
Below the diagonal: gitui.components.revision_files uses a module listed above it, which is the healthy direction.
gitui.components.revision_files uses gitui.components.utils.scroll_vertical, so a change to gitui.components.utils.scroll_vertical can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break gitui.components.utils.scroll_vertical.
Position
Below the diagonal: gitui.components.revision_files uses a module listed above it, which is the healthy direction.
24→39 gitui.components.revision_files uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.revision_files uses a type in gitui.app.
gitui.components.revision_files uses gitui.app, so a change to gitui.app can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break gitui.app.
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.
24→40 gitui.components.revision_files uses gituipart of a loop✕
Connections
1 pair of types, where a type in gitui.components.revision_files uses a type in gitui.
gitui.components.revision_files uses gitui, so a change to gitui can break gitui.components.revision_files, while a change to gitui.components.revision_files can't break gitui.
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.
gitui.popups.branchlist uses asyncgit, so a change to asyncgit can break gitui.popups.branchlist, while a change to gitui.popups.branchlist can't break asyncgit.
Position
Below the diagonal: gitui.popups.branchlist uses a module listed above it, which is the healthy direction.
gitui.popups.branchlist uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.branchlist, while a change to gitui.popups.branchlist can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.branchlist uses a module listed above it, which is the healthy direction.
gitui.popups.branchlist uses gitui.queue, so a change to gitui.queue can break gitui.popups.branchlist, while a change to gitui.popups.branchlist can't break gitui.queue.
Position
Below the diagonal: gitui.popups.branchlist uses a module listed above it, which is the healthy direction.
gitui.popups.branchlist uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.popups.branchlist, while a change to gitui.popups.branchlist can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.popups.branchlist uses a module listed above it, which is the healthy direction.
gitui.popups.branchlist uses gitui.components, so a change to gitui.components can break gitui.popups.branchlist, while a change to gitui.popups.branchlist can't break gitui.components.
Position
Below the diagonal: gitui.popups.branchlist uses a module listed above it, which is the healthy direction.
gitui.popups.branchlist uses gitui.components.utils.scroll_vertical, so a change to gitui.components.utils.scroll_vertical can break gitui.popups.branchlist, while a change to gitui.popups.branchlist can't break gitui.components.utils.scroll_vertical.
Position
Below the diagonal: gitui.popups.branchlist uses a module listed above it, which is the healthy direction.
25→39 gitui.popups.branchlist uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.branchlist uses a type in gitui.app.
gitui.popups.branchlist uses gitui.app, so a change to gitui.app can break gitui.popups.branchlist, while a change to gitui.popups.branchlist can't break gitui.app.
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.
gitui.popups.commit uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.commit, while a change to gitui.popups.commit can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.commit uses a module listed above it, which is the healthy direction.
gitui.popups.commit uses gitui.queue, so a change to gitui.queue can break gitui.popups.commit, while a change to gitui.popups.commit can't break gitui.queue.
Position
Below the diagonal: gitui.popups.commit uses a module listed above it, which is the healthy direction.
gitui.popups.commit uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.popups.commit, while a change to gitui.popups.commit can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.popups.commit uses a module listed above it, which is the healthy direction.
gitui.popups.commit uses asyncgit.sync.status, so a change to asyncgit.sync.status can break gitui.popups.commit, while a change to gitui.popups.commit can't break asyncgit.sync.status.
Position
Below the diagonal: gitui.popups.commit uses a module listed above it, which is the healthy direction.
gitui.popups.commit uses gitui.components, so a change to gitui.components can break gitui.popups.commit, while a change to gitui.popups.commit can't break gitui.components.
Position
Below the diagonal: gitui.popups.commit uses a module listed above it, which is the healthy direction.
gitui.popups.commit uses gitui.components.textinput, so a change to gitui.components.textinput can break gitui.popups.commit, while a change to gitui.popups.commit can't break gitui.components.textinput.
Position
Below the diagonal: gitui.popups.commit uses a module listed above it, which is the healthy direction.
26→39 gitui.popups.commit uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.commit uses a type in gitui.app.
gitui.popups.commit uses gitui.app, so a change to gitui.app can break gitui.popups.commit, while a change to gitui.popups.commit can't break gitui.app.
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.
gitui.tabs.stashing uses gitui.components.command, so a change to gitui.components.command can break gitui.tabs.stashing, while a change to gitui.tabs.stashing can't break gitui.components.command.
Position
Below the diagonal: gitui.tabs.stashing uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.tabs.stashing uses a type in gitui.queue.
The types involved
gitui.tabs.stashing.Stashing → gitui.queue.Queue
Direction
gitui.tabs.stashing uses gitui.queue, so a change to gitui.queue can break gitui.tabs.stashing, while a change to gitui.tabs.stashing can't break gitui.queue.
Position
Below the diagonal: gitui.tabs.stashing uses a module listed above it, which is the healthy direction.
gitui.tabs.stashing uses gitui.components, so a change to gitui.components can break gitui.tabs.stashing, while a change to gitui.tabs.stashing can't break gitui.components.
Position
Below the diagonal: gitui.tabs.stashing uses a module listed above it, which is the healthy direction.
gitui.tabs.stashing uses gitui.components.status_tree, so a change to gitui.components.status_tree can break gitui.tabs.stashing, while a change to gitui.tabs.stashing can't break gitui.components.status_tree.
Position
Below the diagonal: gitui.tabs.stashing uses a module listed above it, which is the healthy direction.
27→39 gitui.tabs.stashing uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.tabs.stashing uses a type in gitui.app.
gitui.tabs.stashing uses gitui.app, so a change to gitui.app can break gitui.tabs.stashing, while a change to gitui.tabs.stashing can't break gitui.app.
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.
gitui.components.commit_details uses gitui.components.command, so a change to gitui.components.command can break gitui.components.commit_details, while a change to gitui.components.commit_details can't break gitui.components.command.
Position
Below the diagonal: gitui.components.commit_details uses a module listed above it, which is the healthy direction.
gitui.components.commit_details uses gitui.components, so a change to gitui.components can break gitui.components.commit_details, while a change to gitui.components.commit_details can't break gitui.components.
Position
Below the diagonal: gitui.components.commit_details uses a module listed above it, which is the healthy direction.
gitui.components.commit_details uses gitui.components.status_tree, so a change to gitui.components.status_tree can break gitui.components.commit_details, while a change to gitui.components.commit_details can't break gitui.components.status_tree.
Position
Below the diagonal: gitui.components.commit_details uses a module listed above it, which is the healthy direction.
gitui.components.commit_details uses gitui.components.commit_details.details, so a change to gitui.components.commit_details.details can break gitui.components.commit_details, while a change to gitui.components.commit_details can't break gitui.components.commit_details.details.
Position
Below the diagonal: gitui.components.commit_details uses a module listed above it, which is the healthy direction.
28→39 gitui.components.commit_details uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.components.commit_details uses a type in gitui.app.
gitui.components.commit_details uses gitui.app, so a change to gitui.app can break gitui.components.commit_details, while a change to gitui.components.commit_details can't break gitui.app.
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.
gitui.popups.fetch uses asyncgit.asyncjob, so a change to asyncgit.asyncjob can break gitui.popups.fetch, while a change to gitui.popups.fetch can't break asyncgit.asyncjob.
Position
Below the diagonal: gitui.popups.fetch uses a module listed above it, which is the healthy direction.
gitui.popups.fetch uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.fetch, while a change to gitui.popups.fetch can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.fetch uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.popups.fetch uses a type in gitui.queue.
The types involved
gitui.popups.fetch.FetchPopup → gitui.queue.Queue
Direction
gitui.popups.fetch uses gitui.queue, so a change to gitui.queue can break gitui.popups.fetch, while a change to gitui.popups.fetch can't break gitui.queue.
Position
Below the diagonal: gitui.popups.fetch uses a module listed above it, which is the healthy direction.
gitui.popups.fetch uses asyncgit.sync.cred, so a change to asyncgit.sync.cred can break gitui.popups.fetch, while a change to gitui.popups.fetch can't break asyncgit.sync.cred.
Position
Below the diagonal: gitui.popups.fetch uses a module listed above it, which is the healthy direction.
gitui.popups.fetch uses gitui.components, so a change to gitui.components can break gitui.popups.fetch, while a change to gitui.popups.fetch can't break gitui.components.
Position
Below the diagonal: gitui.popups.fetch uses a module listed above it, which is the healthy direction.
gitui.popups.fetch uses gitui.components.cred, so a change to gitui.components.cred can break gitui.popups.fetch, while a change to gitui.popups.fetch can't break gitui.components.cred.
Position
Below the diagonal: gitui.popups.fetch uses a module listed above it, which is the healthy direction.
29→39 gitui.popups.fetch uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.fetch uses a type in gitui.app.
gitui.popups.file_revlog uses asyncgit, so a change to asyncgit can break gitui.popups.file_revlog, while a change to gitui.popups.file_revlog can't break asyncgit.
Position
Below the diagonal: gitui.popups.file_revlog uses a module listed above it, which is the healthy direction.
gitui.popups.file_revlog uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.file_revlog, while a change to gitui.popups.file_revlog can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.file_revlog uses a module listed above it, which is the healthy direction.
gitui.popups.file_revlog uses gitui.queue, so a change to gitui.queue can break gitui.popups.file_revlog, while a change to gitui.popups.file_revlog can't break gitui.queue.
Position
Below the diagonal: gitui.popups.file_revlog uses a module listed above it, which is the healthy direction.
gitui.popups.file_revlog uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.popups.file_revlog, while a change to gitui.popups.file_revlog can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.popups.file_revlog uses a module listed above it, which is the healthy direction.
gitui.popups.file_revlog uses gitui.components, so a change to gitui.components can break gitui.popups.file_revlog, while a change to gitui.popups.file_revlog can't break gitui.components.
Position
Below the diagonal: gitui.popups.file_revlog uses a module listed above it, which is the healthy direction.
gitui.popups.file_revlog uses gitui.components.diff, so a change to gitui.components.diff can break gitui.popups.file_revlog, while a change to gitui.popups.file_revlog can't break gitui.components.diff.
Position
Below the diagonal: gitui.popups.file_revlog uses a module listed above it, which is the healthy direction.
30→39 gitui.popups.file_revlog uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.file_revlog uses a type in gitui.app.
gitui.popups.file_revlog uses gitui.app, so a change to gitui.app can break gitui.popups.file_revlog, while a change to gitui.popups.file_revlog can't break gitui.app.
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.
gitui.popups.log_search uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.log_search, while a change to gitui.popups.log_search can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.log_search uses a module listed above it, which is the healthy direction.
gitui.popups.log_search uses gitui.queue, so a change to gitui.queue can break gitui.popups.log_search, while a change to gitui.popups.log_search can't break gitui.queue.
Position
Below the diagonal: gitui.popups.log_search uses a module listed above it, which is the healthy direction.
gitui.popups.log_search uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.popups.log_search, while a change to gitui.popups.log_search can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.popups.log_search uses a module listed above it, which is the healthy direction.
gitui.popups.log_search uses gitui.components, so a change to gitui.components can break gitui.popups.log_search, while a change to gitui.popups.log_search can't break gitui.components.
Position
Below the diagonal: gitui.popups.log_search uses a module listed above it, which is the healthy direction.
gitui.popups.log_search uses gitui.components.textinput, so a change to gitui.components.textinput can break gitui.popups.log_search, while a change to gitui.popups.log_search can't break gitui.components.textinput.
Position
Below the diagonal: gitui.popups.log_search uses a module listed above it, which is the healthy direction.
gitui.popups.log_search uses gitui.components.diff, so a change to gitui.components.diff can break gitui.popups.log_search, while a change to gitui.popups.log_search can't break gitui.components.diff.
Position
Below the diagonal: gitui.popups.log_search uses a module listed above it, which is the healthy direction.
31→39 gitui.popups.log_search uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.log_search uses a type in gitui.app.
gitui.popups.log_search uses gitui.app, so a change to gitui.app can break gitui.popups.log_search, while a change to gitui.popups.log_search can't break gitui.app.
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.
gitui.popups.pull uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.pull, while a change to gitui.popups.pull can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.pull uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.popups.pull uses a type in gitui.queue.
The types involved
gitui.popups.pull.PullPopup → gitui.queue.Queue
Direction
gitui.popups.pull uses gitui.queue, so a change to gitui.queue can break gitui.popups.pull, while a change to gitui.popups.pull can't break gitui.queue.
Position
Below the diagonal: gitui.popups.pull uses a module listed above it, which is the healthy direction.
gitui.popups.pull uses asyncgit.sync.cred, so a change to asyncgit.sync.cred can break gitui.popups.pull, while a change to gitui.popups.pull can't break asyncgit.sync.cred.
Position
Below the diagonal: gitui.popups.pull uses a module listed above it, which is the healthy direction.
gitui.popups.pull uses gitui.components, so a change to gitui.components can break gitui.popups.pull, while a change to gitui.popups.pull can't break gitui.components.
Position
Below the diagonal: gitui.popups.pull uses a module listed above it, which is the healthy direction.
gitui.popups.pull uses gitui.components.cred, so a change to gitui.components.cred can break gitui.popups.pull, while a change to gitui.popups.pull can't break gitui.components.cred.
Position
Below the diagonal: gitui.popups.pull uses a module listed above it, which is the healthy direction.
32→39 gitui.popups.pull uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.pull uses a type in gitui.app.
gitui.popups.push uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.push, while a change to gitui.popups.push can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.push uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.popups.push uses a type in gitui.queue.
The types involved
gitui.popups.push.PushPopup → gitui.queue.Queue
Direction
gitui.popups.push uses gitui.queue, so a change to gitui.queue can break gitui.popups.push, while a change to gitui.popups.push can't break gitui.queue.
Position
Below the diagonal: gitui.popups.push uses a module listed above it, which is the healthy direction.
gitui.popups.push uses asyncgit.sync.cred, so a change to asyncgit.sync.cred can break gitui.popups.push, while a change to gitui.popups.push can't break asyncgit.sync.cred.
Position
Below the diagonal: gitui.popups.push uses a module listed above it, which is the healthy direction.
gitui.popups.push uses gitui.components, so a change to gitui.components can break gitui.popups.push, while a change to gitui.popups.push can't break gitui.components.
Position
Below the diagonal: gitui.popups.push uses a module listed above it, which is the healthy direction.
gitui.popups.push uses asyncgit.sync.remotes.push, so a change to asyncgit.sync.remotes.push can break gitui.popups.push, while a change to gitui.popups.push can't break asyncgit.sync.remotes.push.
Position
Below the diagonal: gitui.popups.push uses a module listed above it, which is the healthy direction.
gitui.popups.push uses gitui.components.cred, so a change to gitui.components.cred can break gitui.popups.push, while a change to gitui.popups.push can't break gitui.components.cred.
Position
Below the diagonal: gitui.popups.push uses a module listed above it, which is the healthy direction.
33→39 gitui.popups.push uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.push uses a type in gitui.app.
gitui.popups.push_tags uses asyncgit, so a change to asyncgit can break gitui.popups.push_tags, while a change to gitui.popups.push_tags can't break asyncgit.
Position
Below the diagonal: gitui.popups.push_tags uses a module listed above it, which is the healthy direction.
gitui.popups.push_tags uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.push_tags, while a change to gitui.popups.push_tags can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.push_tags uses a module listed above it, which is the healthy direction.
gitui.popups.push_tags uses gitui.queue, so a change to gitui.queue can break gitui.popups.push_tags, while a change to gitui.popups.push_tags can't break gitui.queue.
Position
Below the diagonal: gitui.popups.push_tags uses a module listed above it, which is the healthy direction.
gitui.popups.push_tags uses asyncgit.sync.cred, so a change to asyncgit.sync.cred can break gitui.popups.push_tags, while a change to gitui.popups.push_tags can't break asyncgit.sync.cred.
Position
Below the diagonal: gitui.popups.push_tags uses a module listed above it, which is the healthy direction.
gitui.popups.push_tags uses gitui.components, so a change to gitui.components can break gitui.popups.push_tags, while a change to gitui.popups.push_tags can't break gitui.components.
Position
Below the diagonal: gitui.popups.push_tags uses a module listed above it, which is the healthy direction.
gitui.popups.push_tags uses gitui.components.cred, so a change to gitui.components.cred can break gitui.popups.push_tags, while a change to gitui.popups.push_tags can't break gitui.components.cred.
Position
Below the diagonal: gitui.popups.push_tags uses a module listed above it, which is the healthy direction.
34→39 gitui.popups.push_tags uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.push_tags uses a type in gitui.app.
gitui.popups.push_tags uses gitui.app, so a change to gitui.app can break gitui.popups.push_tags, while a change to gitui.popups.push_tags can't break gitui.app.
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.
gitui.tabs.status uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break gitui.tabs.status, while a change to gitui.tabs.status can't break asyncgit.sync.repository.
Position
Below the diagonal: gitui.tabs.status uses a module listed above it, which is the healthy direction.
gitui.tabs.status uses gitui.components.command, so a change to gitui.components.command can break gitui.tabs.status, while a change to gitui.tabs.status can't break gitui.components.command.
Position
Below the diagonal: gitui.tabs.status uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in gitui.tabs.status uses a type in gitui.queue.
The types involved
gitui.tabs.status.Status → gitui.queue.Queue
gitui.tabs.status.Status → gitui.queue.ResetItem
Direction
gitui.tabs.status uses gitui.queue, so a change to gitui.queue can break gitui.tabs.status, while a change to gitui.tabs.status can't break gitui.queue.
Position
Below the diagonal: gitui.tabs.status uses a module listed above it, which is the healthy direction.
gitui.tabs.status uses gitui.components, so a change to gitui.components can break gitui.tabs.status, while a change to gitui.tabs.status can't break gitui.components.
Position
Below the diagonal: gitui.tabs.status uses a module listed above it, which is the healthy direction.
gitui.tabs.status uses gitui.components.diff, so a change to gitui.components.diff can break gitui.tabs.status, while a change to gitui.tabs.status can't break gitui.components.diff.
Position
Below the diagonal: gitui.tabs.status uses a module listed above it, which is the healthy direction.
gitui.tabs.status uses gitui.components.revision_files, so a change to gitui.components.revision_files can break gitui.tabs.status, while a change to gitui.tabs.status can't break gitui.components.revision_files.
Position
Below the diagonal: gitui.tabs.status uses a module listed above it, which is the healthy direction.
35→39 gitui.tabs.status uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.tabs.status uses a type in gitui.app.
The types involved
gitui.tabs.status.Status → gitui.app.Environment
Direction
gitui.tabs.status uses gitui.app, so a change to gitui.app can break gitui.tabs.status, while a change to gitui.tabs.status can't break gitui.app.
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.
gitui.popups.inspect_commit uses asyncgit, so a change to asyncgit can break gitui.popups.inspect_commit, while a change to gitui.popups.inspect_commit can't break asyncgit.
Position
Below the diagonal: gitui.popups.inspect_commit uses a module listed above it, which is the healthy direction.
gitui.popups.inspect_commit uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.inspect_commit, while a change to gitui.popups.inspect_commit can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.inspect_commit uses a module listed above it, which is the healthy direction.
gitui.popups.inspect_commit uses gitui.queue, so a change to gitui.queue can break gitui.popups.inspect_commit, while a change to gitui.popups.inspect_commit can't break gitui.queue.
Position
Below the diagonal: gitui.popups.inspect_commit uses a module listed above it, which is the healthy direction.
gitui.popups.inspect_commit uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.popups.inspect_commit, while a change to gitui.popups.inspect_commit can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.popups.inspect_commit uses a module listed above it, which is the healthy direction.
gitui.popups.inspect_commit uses gitui.components, so a change to gitui.components can break gitui.popups.inspect_commit, while a change to gitui.popups.inspect_commit can't break gitui.components.
Position
Below the diagonal: gitui.popups.inspect_commit uses a module listed above it, which is the healthy direction.
gitui.popups.inspect_commit uses gitui.components.diff, so a change to gitui.components.diff can break gitui.popups.inspect_commit, while a change to gitui.popups.inspect_commit can't break gitui.components.diff.
Position
Below the diagonal: gitui.popups.inspect_commit uses a module listed above it, which is the healthy direction.
gitui.popups.inspect_commit uses gitui.components.commit_details, so a change to gitui.components.commit_details can break gitui.popups.inspect_commit, while a change to gitui.popups.inspect_commit can't break gitui.components.commit_details.
Position
Below the diagonal: gitui.popups.inspect_commit uses a module listed above it, which is the healthy direction.
36→39 gitui.popups.inspect_commit uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.inspect_commit uses a type in gitui.app.
gitui.popups.inspect_commit uses gitui.app, so a change to gitui.app can break gitui.popups.inspect_commit, while a change to gitui.popups.inspect_commit can't break gitui.app.
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.
gitui.tabs.revlog uses asyncgit.asyncjob, so a change to asyncgit.asyncjob can break gitui.tabs.revlog, while a change to gitui.tabs.revlog can't break asyncgit.asyncjob.
Position
Below the diagonal: gitui.tabs.revlog uses a module listed above it, which is the healthy direction.
gitui.tabs.revlog uses gitui.components.command, so a change to gitui.components.command can break gitui.tabs.revlog, while a change to gitui.tabs.revlog can't break gitui.components.command.
Position
Below the diagonal: gitui.tabs.revlog uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.tabs.revlog uses a type in gitui.queue.
The types involved
gitui.tabs.revlog.Revlog → gitui.queue.Queue
Direction
gitui.tabs.revlog uses gitui.queue, so a change to gitui.queue can break gitui.tabs.revlog, while a change to gitui.tabs.revlog can't break gitui.queue.
Position
Below the diagonal: gitui.tabs.revlog uses a module listed above it, which is the healthy direction.
gitui.tabs.revlog uses asyncgit.sync.commits_info, so a change to asyncgit.sync.commits_info can break gitui.tabs.revlog, while a change to gitui.tabs.revlog can't break asyncgit.sync.commits_info.
Position
Below the diagonal: gitui.tabs.revlog uses a module listed above it, which is the healthy direction.
gitui.tabs.revlog uses gitui.components, so a change to gitui.components can break gitui.tabs.revlog, while a change to gitui.tabs.revlog can't break gitui.components.
Position
Below the diagonal: gitui.tabs.revlog uses a module listed above it, which is the healthy direction.
gitui.tabs.revlog uses gitui.components.commitlist, so a change to gitui.components.commitlist can break gitui.tabs.revlog, while a change to gitui.tabs.revlog can't break gitui.components.commitlist.
Position
Below the diagonal: gitui.tabs.revlog uses a module listed above it, which is the healthy direction.
gitui.tabs.revlog uses gitui.components.commit_details, so a change to gitui.components.commit_details can break gitui.tabs.revlog, while a change to gitui.tabs.revlog can't break gitui.components.commit_details.
Position
Below the diagonal: gitui.tabs.revlog uses a module listed above it, which is the healthy direction.
37→39 gitui.tabs.revlog uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.tabs.revlog uses a type in gitui.app.
The types involved
gitui.tabs.revlog.Revlog → gitui.app.Environment
Direction
gitui.tabs.revlog uses gitui.app, so a change to gitui.app can break gitui.tabs.revlog, while a change to gitui.tabs.revlog can't break gitui.app.
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.
gitui.popups.compare_commits uses asyncgit, so a change to asyncgit can break gitui.popups.compare_commits, while a change to gitui.popups.compare_commits can't break asyncgit.
Position
Below the diagonal: gitui.popups.compare_commits uses a module listed above it, which is the healthy direction.
gitui.popups.compare_commits uses gitui.components.command, so a change to gitui.components.command can break gitui.popups.compare_commits, while a change to gitui.popups.compare_commits can't break gitui.components.command.
Position
Below the diagonal: gitui.popups.compare_commits uses a module listed above it, which is the healthy direction.
gitui.popups.compare_commits uses gitui.queue, so a change to gitui.queue can break gitui.popups.compare_commits, while a change to gitui.popups.compare_commits can't break gitui.queue.
Position
Below the diagonal: gitui.popups.compare_commits uses a module listed above it, which is the healthy direction.
gitui.popups.compare_commits uses gitui.components, so a change to gitui.components can break gitui.popups.compare_commits, while a change to gitui.popups.compare_commits can't break gitui.components.
Position
Below the diagonal: gitui.popups.compare_commits uses a module listed above it, which is the healthy direction.
gitui.popups.compare_commits uses gitui.components.diff, so a change to gitui.components.diff can break gitui.popups.compare_commits, while a change to gitui.popups.compare_commits can't break gitui.components.diff.
Position
Below the diagonal: gitui.popups.compare_commits uses a module listed above it, which is the healthy direction.
gitui.popups.compare_commits uses gitui.components.commit_details, so a change to gitui.components.commit_details can break gitui.popups.compare_commits, while a change to gitui.popups.compare_commits can't break gitui.components.commit_details.
Position
Below the diagonal: gitui.popups.compare_commits uses a module listed above it, which is the healthy direction.
gitui.popups.compare_commits uses gitui.popups.inspect_commit, so a change to gitui.popups.inspect_commit can break gitui.popups.compare_commits, while a change to gitui.popups.compare_commits can't break gitui.popups.inspect_commit.
Position
Below the diagonal: gitui.popups.compare_commits uses a module listed above it, which is the healthy direction.
38→39 gitui.popups.compare_commits uses gitui.apppart of a loop✕
Connections
1 pair of types, where a type in gitui.popups.compare_commits uses a type in gitui.app.
gitui.popups.compare_commits uses gitui.app, so a change to gitui.app can break gitui.popups.compare_commits, while a change to gitui.popups.compare_commits can't break gitui.app.
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.
gitui.app uses gitui.components.command, so a change to gitui.components.command can break gitui.app, while a change to gitui.app can't break gitui.components.command.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui.app uses gitui.popups.blame_file, so a change to gitui.popups.blame_file can break gitui.app, while a change to gitui.app can't break gitui.popups.blame_file.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui.app uses gitui.popups.checkout_option, so a change to gitui.popups.checkout_option can break gitui.app, while a change to gitui.app can't break gitui.popups.checkout_option.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.app uses a type in gitui.popups.taglist.
The types involved
gitui.app.App → gitui.popups.taglist.TagListPopup
Direction
gitui.app uses gitui.popups.taglist, so a change to gitui.popups.taglist can break gitui.app, while a change to gitui.app can't break gitui.popups.taglist.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui.app uses gitui.popups.branchlist, so a change to gitui.popups.branchlist can break gitui.app, while a change to gitui.app can't break gitui.popups.branchlist.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.app uses a type in gitui.popups.commit.
The types involved
gitui.app.App → gitui.popups.commit.CommitPopup
Direction
gitui.app uses gitui.popups.commit, so a change to gitui.popups.commit can break gitui.app, while a change to gitui.app can't break gitui.popups.commit.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in gitui.app uses a type in gitui.tabs.stashing.
The types involved
gitui.app.App → gitui.tabs.stashing.Stashing
Direction
gitui.app uses gitui.tabs.stashing, so a change to gitui.tabs.stashing can break gitui.app, while a change to gitui.app can't break gitui.tabs.stashing.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui.app uses gitui.popups.file_revlog, so a change to gitui.popups.file_revlog can break gitui.app, while a change to gitui.app can't break gitui.popups.file_revlog.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui.app uses gitui.popups.log_search, so a change to gitui.popups.log_search can break gitui.app, while a change to gitui.app can't break gitui.popups.log_search.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui.app uses gitui.popups.push_tags, so a change to gitui.popups.push_tags can break gitui.app, while a change to gitui.app can't break gitui.popups.push_tags.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui.app uses gitui.popups.inspect_commit, so a change to gitui.popups.inspect_commit can break gitui.app, while a change to gitui.app can't break gitui.popups.inspect_commit.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui.app uses gitui.popups.compare_commits, so a change to gitui.popups.compare_commits can break gitui.app, while a change to gitui.app can't break gitui.popups.compare_commits.
Position
Below the diagonal: gitui.app uses a module listed above it, which is the healthy direction.
gitui uses asyncgit.sync.repository, so a change to asyncgit.sync.repository can break gitui, while a change to gitui can't break asyncgit.sync.repository.
Position
Below the diagonal: gitui 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
55
High / Critical
A03:2025 — Software Supply Chain Failures
16
Medium
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs; 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; Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with diff.rs (2), revision_files.rs (2), filetree.rs (2).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
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.
Code Duplication: Edited copies of one member (3 members, 16+ corresponding lines)
src/app.rs
6.0
Mixed
Explicit Debt: TodoComment
src/components/diff.rs
6.0
Mixed
Explicit Debt: TodoComment
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 — 49
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 — 400
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 — 110
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 19
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 42 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, 523 of 559 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's 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.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's 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.
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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, 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.
X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check 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.
X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's 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
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
17 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was App::process_internal_event at 47. A further 4 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 TextInputComponent::process_inputs at 26 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/components/textinput.rs (TextInputComponent::process_inputs at 26), src/popups/confirm.rs (ConfirmPopup::get_text at 17), src/keys/key_config.rs (KeyConfig::get_key_symbol at 16). 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.
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with App::process_internal_event (cyclomatic 47), Status::event (cyclomatic 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 7.4 to about 7.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 24 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 30 down to 30 or less in Cognitive Complexity — start with asyncgit::sync::staging::apply_selection (cognitive 61), DiffComponent::event (cognitive 48), Status::event (cognitive 45). — 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 8 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.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 FileTooLong finding(s) in God Classes — start with strings.rs, app.rs, status.rs. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 ClassTooLong finding(s) in God Classes — start with app.rs, status.rs, diff.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 4 MethodTooLong finding(s) in God Classes — start with textinput.rs, app.rs, revlog.rs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
75 duplicated block group(s) detected. 9.3 % of the production lines (4,050 of 43,639) are in a reported copy. A further 62 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 82 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with blame.rs, REDACTED, fetch.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with remote_tags.rs, commit_files.rs, branchlist.rs. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 4 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with mod.rs, checkout_option.rs, commit_revert.rs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling6.6 / 10Adequate✓ 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.
7 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 3 module(s) off the main sequence, with abstractness counted on 5 of the 7 (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: filetreelist · ×3
What to do
Resolve the 3 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with callbacks.rs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage7.8 / 10Strong✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 40.7% — 81 file(s) below 50%. Measured from the Rust suite (repository root: `cargo test --workspace` instrumented over 154 production file(s), 7 test binaries and 1 doc-test binaries).
Resolve the 81 Low coverage finding(s) in Code Coverage — start with mod.rs (3), diff.rs (2), lib.rs (2). — One of this dimension's main actionable groups (81 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
24 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
Outdated: anyhow · ×24
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 435 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
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.
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.
4 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is asyncgit/src/revlog.rs. Counted over 127 of the 161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
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.
73 deducted task-comment markers across 43639 LoC (0.2/KLoC) → score 9.7. 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.
TodoComment · ×71src/app.rs:279
HackComment · ×2asyncgit/src/sync/commit.rs:31
What to do
Resolve the 71 TodoComment finding(s) in Explicit Debt — start with app.rs (8), diff.rs (7), cred.rs (7). — One of this dimension's main actionable groups (71 warning-level).
Resolve the 2 HackComment finding(s) in Explicit Debt — start with commit.rs, reword.rs. — One of this dimension's main actionable groups (2 warning-level).
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. 8 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
2 of 7 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).
55 finding(s): 0 critical, 49 high, 6 medium, 0 low. 39 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.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
No action in Static Analysis (SAST) — all 39 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 (39 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 5 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
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.
66 of 127 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is asyncgit/src/sync/branch/mod.rs. Counted over 127 of the 161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned file · ×64src/ui/reflow.rs:1
Most significant orphaned file · ×2asyncgit/src/sync/branch/mod.rs:1
Concentrated knowledge decay
What to do
Resolve the 64 Orphaned file finding(s) in Knowledge Freshness — start with diff.rs (2), revision_files.rs (2), filetree.rs (2). — One of this dimension's main actionable groups (64 recommendation-level).
Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with mod.rs, filetreeitems.rs. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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?
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?
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 — 1 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 — 9 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 — 73 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
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 — ~42 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.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — N/A — too few peers to establish a naming convention (4826 declarations, no unit with a dominant convention).
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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .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.
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
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 3 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — 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 — coverage data present for 154 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — No web surface: 160 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.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X3 Exception handling — 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
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
TodoComment src/app.rs:279— //TODO: component property + a macro `fullscreen_popup_open!` — 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 src/app.rs:289— //TODO: macro because of generic draw call — 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 src/app.rs:401— //TODO: do we need this? — 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 src/app.rs:445— //TODO: better system for this — 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 src/app.rs:676— //TODO: make this a queue event? — 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 src/app.rs:921— //TODO: validate this is a valid repo first, so we can show proper error otherwise — 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 src/app.rs:1065— //TODO: check if this is correct based on the fix in `c6abbaf` — 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 src/app.rs:1159— //TODO: make this dynamic — 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 src/main.rs:59— //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 asyncgit/src/lib.rs:39— //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 asyncgit/src/sync/commit_filter.rs:49— //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 src/string_utils.rs:18— //TODO: allow customize tabsize — 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 src/tabs/revlog.rs:50— //TODO: deserves its own component — 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 src/tabs/revlog.rs:450— //TODO: cleanup — 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 src/popups/branchlist.rs:121— //TODO: cleanup — 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 asyncgit/src/sync/remotes/push.rs:132— //TODO: cleanup — 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 src/tabs/stashing.rs:75— //TODO: support options — 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 src/popups/externaleditor.rs:80— // TODO: proper handling arguments containing whitespaces — 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 src/popups/options.rs:111— //TODO: use style — 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 src/popups/submodules.rs:296— //TODO: dedup this almost identical with BranchListComponent — 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 src/keys/symbols.rs:66— //TODO: this could auto generated in a proc macro — 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 src/components/changes.rs:100— //TODO: check if we can handle the one file case with it as well — 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 src/components/changes.rs:108— //TODO: this might be slow in big repos, — 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 src/components/commitlist.rs:322— //TODO: support this? — 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 src/components/diff.rs:573— //TODO: support untracked files as well — 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.
FileTooLong: src/strings.rs src/strings.rs— FileTooLong — 1410 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 910 over it, 2.82× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/app.rs src/app.rs— FileTooLong — 878 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: App (3 blocks, 70-1229). The bar is 500 significant lines; this is 378 over it, 1.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: tabs/status.rs src/tabs/status.rs— FileTooLong — 667 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: Status (4 blocks, 65-980). The bar is 500 significant lines; this is 167 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: components/diff.rs src/components/diff.rs— FileTooLong — 657 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 90% of them inside a single declaration: DiffComponent (4 blocks, 105-961). The bar is 500 significant lines; this is 157 over it, 1.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: components/commitlist.rs src/components/commitlist.rs— FileTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 95% of them inside a single declaration: CommitList (4 blocks, 40-895). The bar is 500 significant lines; this is 81 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 87% of them inside a single declaration: BlameFilePopup (4 blocks, 86-799). The bar is 500 significant lines; this is 49 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: popups/branchlist.rs src/popups/branchlist.rs— FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 94% of them inside a single declaration: BranchListPopup (4 blocks, 45-790). The bar is 500 significant lines; this is 49 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: components/textinput.rs src/components/textinput.rs— FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 94% of them inside a single declaration: TextInputComponent (4 blocks, 43-731). The bar is 500 significant lines; this is 30 over it, 1.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: tabs/revlog.rs src/tabs/revlog.rs— FileTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 91% of them inside a single declaration: Revlog (4 blocks, 63-762). The bar is 500 significant lines; this is 16 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
ClassTooLong: App src/app.rs:70— ClassTooLong — 814 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 27 methods, 3 blocks, lines 70-1229. The bar is 400 significant lines; this is 414 over it, 2.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Status src/tabs/status.rs:65— ClassTooLong — 622 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 35 methods, 4 blocks, lines 65-980. The bar is 400 significant lines; this is 222 over it, 1.56× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DiffComponent src/components/diff.rs:105— ClassTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 29 methods, 4 blocks, lines 105-961. The bar is 400 significant lines; this is 189 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CommitList src/components/commitlist.rs:40— ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 39 methods, 4 blocks, lines 40-895. The bar is 400 significant lines; this is 150 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BranchListPopup src/popups/branchlist.rs:45— ClassTooLong — 516 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 24 methods, 4 blocks, lines 45-790. The bar is 400 significant lines; this is 116 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TextInputComponent src/components/textinput.rs:43— ClassTooLong — 499 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 15 methods, 4 blocks, lines 43-731. The bar is 400 significant lines; this is 99 over it, 1.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BlameFilePopup REDACTED:86— ClassTooLong — 478 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 20 methods, 4 blocks, lines 86-799. The bar is 400 significant lines; this is 78 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Revlog src/tabs/revlog.rs:63— ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 4 blocks, lines 63-762. The bar is 400 significant lines; this is 69 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (8 lines × 2) asyncgit/src/blame.rs:48— asyncgit/src/blame.rs:48-55 | asyncgit/src/diff.rs:66-73 — before extracting anything, compare `asyncgit/src/blame.rs` and `asyncgit/src/diff.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) REDACTED:295— REDACTED:295-305 | src/popups/file_revlog.rs:517-524 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:295` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (8 lines × 2) src/popups/fetch.rs:173— src/popups/fetch.rs:173-180 | src/popups/pull.rs:260-267 — before extracting anything, compare `src/popups/fetch.rs` and `src/popups/pull.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/fetch.rs:173` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) asyncgit/src/branches.rs:26— asyncgit/src/branches.rs:26-33 | asyncgit/src/treefiles.rs:31-38 — 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) asyncgit/src/fetch_job.rs:31— asyncgit/src/fetch_job.rs:31-38 | asyncgit/src/remote_tags.rs:34-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. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/fetch_job.rs:31` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) src/popups/compare_commits.rs:152— src/popups/compare_commits.rs:152-159 | src/popups/inspect_commit.rs:207-214 — before extracting anything, compare `src/popups/compare_commits.rs` and `src/popups/inspect_commit.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 148 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) asyncgit/src/sync/remotes/mod.rs:161— asyncgit/src/sync/remotes/mod.rs:161-168 | asyncgit/src/sync/remotes/mod.rs:211-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/sync/remotes/mod.rs:161` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) asyncgit/src/remote_tags.rs:45— asyncgit/src/remote_tags.rs:45-55 | src/ui/syntax_text.rs:252-262 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) asyncgit/src/sync/commit_files.rs:106— asyncgit/src/sync/commit_files.rs:106-116 | asyncgit/src/sync/commit_files.rs:146-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/sync/commit_files.rs:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/popups/branchlist.rs:62— src/popups/branchlist.rs:62-72 | REDACTED:59-69 — 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) src/popups/checkout_option.rs:67— src/popups/checkout_option.rs:67-77 | src/popups/reset.rs:99-109 — before extracting anything, compare `src/popups/checkout_option.rs` and `src/popups/reset.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/checkout_option.rs:67` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) asyncgit/src/push.rs:136— asyncgit/src/push.rs:136-146 | asyncgit/src/push_tags.rs:119-129 — before extracting anything, compare `asyncgit/src/push.rs` and `asyncgit/src/push_tags.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `_params` to `&PushRequest` in one and `&PushTagsRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) src/popups/compare_commits.rs:209— src/popups/compare_commits.rs:209-219 | src/popups/inspect_commit.rs:254-264 — before extracting anything, compare `src/popups/compare_commits.rs` and `src/popups/inspect_commit.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/compare_commits.rs:209` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×5
MethodTooLong: TextInputComponent.process_inputs src/components/textinput.rs:263— MethodTooLong — process_inputs runs 304 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 204 over it, 3.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: App.process_internal_event src/app.rs:739— MethodTooLong — process_internal_event runs 147 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 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Revlog.event src/tabs/revlog.rs:452— MethodTooLong — event runs 120 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 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Status.event src/tabs/status.rs:815— MethodTooLong — event runs 109 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×4
Edited copy of a member (11 corresponding lines) asyncgit/src/sync/branch/mod.rs:241— asyncgit/src/sync/branch/mod.rs:241-251 | asyncgit/src/sync/branch/mod.rs:260-270 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/popups/checkout_option.rs:39— src/popups/checkout_option.rs:39-49 | src/popups/reset.rs:55-68 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) asyncgit/src/sync/commit_revert.rs:14— asyncgit/src/sync/commit_revert.rs:14-24 | asyncgit/src/sync/reset.rs:46-56 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) src/popups/push.rs:217— src/popups/push.rs:217-227 | src/popups/push_tags.rs:151-161 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×4
Edited copy of a member (15 corresponding lines) src/popups/compare_commits.rs:166— src/popups/compare_commits.rs:166-181 | src/popups/inspect_commit.rs:221-235 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/popups/push.rs:193— src/popups/push.rs:193-207 | src/popups/push_tags.rs:127-141 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/popups/branchlist.rs:242— src/popups/branchlist.rs:242-256 | src/popups/submodules.rs:243-257 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) src/popups/branchlist.rs:348— src/popups/branchlist.rs:348-362 | src/popups/branchlist.rs:364-378 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (7 lines × 2) asyncgit/src/sync/sign.rs:263— asyncgit/src/sync/sign.rs:263-269 | asyncgit/src/sync/sign.rs:341-347 — 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) filetreelist/src/filetreeitems.rs:200— filetreelist/src/filetreeitems.rs:200-206 | filetreelist/src/filetreeitems.rs:245-251 — 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) src/popups/fetch.rs:63— src/popups/fetch.rs:63-69 | src/popups/push_tags.rs:66-72 — before extracting anything, compare `src/popups/fetch.rs` and `src/popups/push_tags.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/fetch.rs:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) asyncgit/src/blame.rs:67— asyncgit/src/blame.rs:67-73 | asyncgit/src/diff.rs:83-89 — before extracting anything, compare `asyncgit/src/blame.rs` and `asyncgit/src/diff.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 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.
asyncgit::sync::staging::apply_selection (cognitive 61) asyncgit/src/sync/staging/mod.rs:77— asyncgit::sync::staging::apply_selection has cognitive complexity 61 (threshold 15). Drivers by points: if/else 18 (49 pts), boolean chains 8, loops 2 (4 pts) (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
asyncgit::sync::diff::raw_diff_to_file_diff (cognitive 23) asyncgit/src/sync/diff.rs:257— asyncgit::sync::diff::raw_diff_to_file_diff has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (21 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
asyncgit::sync::status::get_status (cognitive 19) asyncgit/src/sync/status.rs:171— asyncgit::sync::status::get_status has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), match/switch 2 (4 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.
Revlog::event (cognitive 38) src/tabs/revlog.rs:452— Revlog::event has cognitive complexity 38 (threshold 15). Drivers by points: if/else 21 (30 pts), boolean chains 8 (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.
Revlog::commands (cognitive 27) src/tabs/revlog.rs:615— Revlog::commands has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 26, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Revlog::update_git (cognitive 20) src/tabs/revlog.rs:154— Revlog::update_git has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (16 lines × 2) src/popups/branchlist.rs:80— src/popups/branchlist.rs:80-95 | src/popups/submodules.rs:66-81 — before extracting anything, compare `src/popups/branchlist.rs` and `src/popups/submodules.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/branchlist.rs:80` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/popups/submodules.rs:106— src/popups/submodules.rs:106-121 | REDACTED:142-157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/submodules.rs:106` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/components/utils/scroll_horizontal.rs:102— src/components/utils/scroll_horizontal.rs:102-117 | src/components/utils/scroll_vertical.rs:136-151 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/components/utils/scroll_horizontal.rs:102` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/popups/checkout_option.rs:199— src/popups/checkout_option.rs:199-211 | src/popups/reset.rs:229-241 — before extracting anything, compare `src/popups/checkout_option.rs` and `src/popups/reset.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/checkout_option.rs:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/popups/push.rs:156— src/popups/push.rs:156-168 | src/popups/push_tags.rs:94-106 — before extracting anything, compare `src/popups/push.rs` and `src/popups/push_tags.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/push.rs:156` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) asyncgit/src/push.rs:161— asyncgit/src/push.rs:161-173 | asyncgit/src/push_tags.rs:144-156 — before extracting anything, compare `asyncgit/src/push.rs` and `asyncgit/src/push_tags.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/push.rs:161` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) asyncgit/src/sync/commits_info.rs:203— asyncgit/src/sync/commits_info.rs:203-212 | asyncgit/src/sync/commits_info.rs:221-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/sync/commits_info.rs:203` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) asyncgit/src/sync/cred.rs:43— asyncgit/src/sync/cred.rs:43-52 | asyncgit/src/sync/cred.rs:78-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/sync/cred.rs:43` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/popups/push.rs:253— src/popups/push.rs:253-262 | src/popups/push_tags.rs:179-188 — before extracting anything, compare `src/popups/push.rs` and `src/popups/push_tags.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/push.rs:253` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) src/popups/compare_commits.rs:169— src/popups/compare_commits.rs:169-177 | src/popups/inspect_commit.rs:224-232 — before extracting anything, compare `src/popups/compare_commits.rs` and `src/popups/inspect_commit.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/popups/compare_commits.rs:179` calls `clone` and `src/popups/inspect_commit.rs:234` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) src/popups/push.rs:313— src/popups/push.rs:313-321 | src/popups/push_tags.rs:235-243 — before extracting anything, compare `src/popups/push.rs` and `src/popups/push_tags.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/push.rs:313` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) asyncgit/src/sync/remotes/mod.rs:127— asyncgit/src/sync/remotes/mod.rs:127-135 | asyncgit/src/sync/reword.rs:73-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/sync/remotes/mod.rs:127` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/popups/push.rs:194— src/popups/push.rs:194-199 | src/popups/push_tags.rs:128-133 — before extracting anything, compare `src/popups/push.rs` and `src/popups/push_tags.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/push.rs:194` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) src/ui/scrollbar.rs:67— src/ui/scrollbar.rs:67-72 | src/ui/scrollbar.rs:109-114 — 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) asyncgit/src/blame.rs:182— asyncgit/src/blame.rs:182-187 | asyncgit/src/diff.rs:215-220 — before extracting anything, compare `asyncgit/src/blame.rs` and `asyncgit/src/diff.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 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.
Off the main sequence: filetreelist — filetreelist: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: scopetime — scopetime: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: git2-hooks — git2-hooks: abstractness 0.25, instability 0.00, distance 0.75 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
App::process_internal_event (cyclomatic 47) src/app.rs:739— App::process_internal_event has cyclomatic complexity 47 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
App::event (cyclomatic 16) src/app.rs:306— App::event 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.
Revlog::event (cyclomatic 30) src/tabs/revlog.rs:452— Revlog::event has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Revlog::commands (cyclomatic 28) src/tabs/revlog.rs:615— Revlog::commands has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
HackComment asyncgit/src/sync/commit.rs:31— // HACK: we undo the last commit and create a new one — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment asyncgit/src/sync/reword.rs:26— // HACK: we undo the last commit and create a new one — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
DiffComponent::event (cognitive 48) src/components/diff.rs:831— DiffComponent::event has cognitive complexity 48 (threshold 15). Drivers by points: if/else 26 (43 pts), boolean chains 5 (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.
DiffComponent::get_text (cognitive 30) src/components/diff.rs:331— DiffComponent::get_text has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (8 pts), boolean chains 3 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Status::event (cognitive 45) src/tabs/status.rs:815— Status::event has cognitive complexity 45 (threshold 15). Drivers by points: if/else 22 (29 pts), boolean chains 12, match/switch 1 (4 pts) (nesting depth added 10). 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.
Status::update_diff (cognitive 16) src/tabs/status.rs:486— Status::update_diff has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (16 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.
RevisionFilesComponent::event (cognitive 34) src/components/revision_files.rs:471— RevisionFilesComponent::event has cognitive complexity 34 (threshold 15). Drivers by points: if/else 18 (33 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RevisionFilesComponent::refresh_files (cognitive 16) src/components/revision_files.rs:125— RevisionFilesComponent::refresh_files has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (16 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BlameFilePopup::event (cognitive 29) REDACTED:252— BlameFilePopup::event has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlameFilePopup::update_syntax (cognitive 16) REDACTED:482— BlameFilePopup::update_syntax has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 1 (2 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
StatusTreeComponent::event (cognitive 28) src/components/status_tree.rs:474— StatusTreeComponent::event has cognitive complexity 28 (threshold 15). Drivers by points: if/else 16 (22 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StatusTreeComponent::build_vec_text_draw_info_for_drawing (cognitive 16) src/components/status_tree.rs:224— StatusTreeComponent::build_vec_text_draw_info_for_drawing 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.
App::event (cognitive 26) src/app.rs:306— App::event has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
App::process_internal_event (cognitive 16) src/app.rs:739— App::process_internal_event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 3 (5 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CommitPopup::event (cognitive 22) src/popups/commit.rs:558— CommitPopup::event has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommitPopup::open (cognitive 17) src/popups/commit.rs:352— CommitPopup::open has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileTreeItems::fold_paths (cognitive 20) filetreelist/src/filetreeitems.rs:326— FileTreeItems::fold_paths has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FileTreeItems::update_visibility (cognitive 19) filetreelist/src/filetreeitems.rs:274— FileTreeItems::update_visibility has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StatusTree::update_visibility (cognitive 19) REDACTED:412— StatusTree::update_visibility has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StatusTree::selection_updown (cognitive 17) REDACTED:209— StatusTree::selection_updown has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 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.
TooManyFunctions: gitui::strings::commands src/strings.rs:545— TooManyFunctions — 115 free functions. The bar is 30 free functions; this is 85 over it, 3.83× 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.
TooManyFunctions: gitui::strings src/strings.rs:52— TooManyFunctions — 87 free functions. The bar is 30 free functions; this is 57 over it, 2.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyFields: KeysList src/keys/key_list.rs:39— TooManyFields — 92 stored fields beside 1 method. The bar is 30 stored fields; this is 62 over it, 3.07× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyFields: App src/app.rs:70— TooManyFields — 49 stored fields beside 27 methods. The bar is 30 stored fields; this is 19 over it, 1.63× the bar. This is width in DATA, not behaviour: every reader that takes the whole type couples to all of its fields, so a change to any one of them is a change every reader has to be checked against. To reduce it, group the fields that are read together by the same callers into a smaller type of their own, and have this one hold that type as a single member — each reader then names only the group it uses.
TooManyMethods: CommitList src/components/commitlist.rs:40— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Status src/tabs/status.rs:65— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) src/popups/fetch.rs:118— src/popups/fetch.rs:118-145 | src/popups/pull.rs:203-232 | src/popups/push.rs:252-285 | src/popups/push_tags.rs:178-207 — 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) src/popups/fetch.rs:153— src/popups/fetch.rs:153-170 | src/popups/pull.rs:240-257 | src/popups/push.rs:293-310 | src/popups/push_tags.rs:215-232 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×2
Edited copy of a member (30 corresponding lines) src/popups/branchlist.rs:258— src/popups/branchlist.rs:258-291 | src/popups/remotelist.rs:192-221 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) REDACTED:715— REDACTED:715-744 | REDACTED:386-416 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×2
Edited copy of a member (37 corresponding lines) asyncgit/src/sync/branch/merge_commit.rs:17— asyncgit/src/sync/branch/merge_commit.rs:17-62 | asyncgit/src/sync/branch/merge_ff.rs:14-50 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (37 corresponding lines) asyncgit/src/revlog.rs:230— asyncgit/src/revlog.rs:230-266 | asyncgit/src/revlog.rs:273-309 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 43+ corresponding lines) · ×2
Edited copies of one member (3 members, 43+ corresponding lines) src/popups/commit.rs:501— src/popups/commit.rs:501-556 | src/popups/remotelist.rs:85-130 | REDACTED:141-183 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 43+ corresponding lines) REDACTED:195— REDACTED:195-250 | src/popups/file_revlog.rs:585-627 | src/popups/log_search.rs:548-600 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 43 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 25+ corresponding lines) · ×2
Edited copies of one member (3 members, 25+ corresponding lines) asyncgit/src/sync/cred.rs:92— asyncgit/src/sync/cred.rs:92-116 | asyncgit/src/sync/cred.rs:122-146 | asyncgit/src/sync/cred.rs:152-176 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 25+ corresponding lines) src/popups/rename_branch.rs:142— src/popups/rename_branch.rs:142-174 | src/popups/rename_remote.rs:149-175 | src/popups/update_remote_url.rs:127-151 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×2
Edited copy of a member (16 corresponding lines) src/components/diff.rs:501— src/components/diff.rs:501-516 | src/components/diff.rs:518-541 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) src/popups/rename_remote.rs:92— src/popups/rename_remote.rs:92-107 | src/popups/update_remote_url.rs:91-110 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×2
Edited copies of one member (3 members, 16+ corresponding lines) src/popups/pull.rs:51— src/popups/pull.rs:51-67 | src/popups/push.rs:70-88 | src/popups/push_tags.rs:47-62 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) src/popups/create_remote.rs:76— src/popups/create_remote.rs:76-91 | src/popups/rename_remote.rs:58-73 | src/popups/update_remote_url.rs:58-73 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×2
Edited copy of a member (22 corresponding lines) src/popups/goto_line.rs:61— src/popups/goto_line.rs:61-82 | src/popups/options.rs:292-315 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) filetreelist/src/filetreeitems.rs:38— filetreelist/src/filetreeitems.rs:38-59 | src/components/utils/filetree.rs:144-167 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×2
Edited copy of a member (19 corresponding lines) src/components/cred.rs:77— src/components/cred.rs:77-96 | src/popups/fuzzy_find.rs:316-334 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) src/components/utils/scroll_horizontal.rs:57— src/components/utils/scroll_horizontal.rs:57-75 | src/components/utils/scroll_vertical.rs:90-109 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) asyncgit/src/sync/cred.rs:39— asyncgit/src/sync/cred.rs:39-52 | asyncgit/src/sync/cred.rs:59-67 | asyncgit/src/sync/cred.rs:74-87 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) asyncgit/src/blame.rs:47— asyncgit/src/blame.rs:47-55 | asyncgit/src/diff.rs:65-73 | asyncgit/src/status.rs:61-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (24 lines × 2) REDACTED:721— REDACTED:721-744 | REDACTED:393-416 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:721` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) src/popups/create_branch.rs:60— src/popups/create_branch.rs:60-83 | src/popups/rename_branch.rs:60-83 — before extracting anything, compare `src/popups/create_branch.rs` and `src/popups/rename_branch.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/create_branch.rs:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) asyncgit/src/blame.rs:87— asyncgit/src/blame.rs:87-108 | asyncgit/src/diff.rs:103-124 — before extracting anything, compare `asyncgit/src/blame.rs` and `asyncgit/src/diff.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/blame.rs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `params` to `BlameParams` in one and `DiffParams` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (22 lines × 2) src/components/commit_details/compare_details.rs:62— src/components/commit_details/compare_details.rs:62-83 | src/components/commit_details/details.rs:161-182 — 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 (19 lines × 2) asyncgit/src/blame.rs:154— asyncgit/src/blame.rs:154-172 | asyncgit/src/diff.rs:191-209 — before extracting anything, compare `asyncgit/src/blame.rs` and `asyncgit/src/diff.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/blame.rs:154` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `params` to `BlameParams` in one and `DiffParams` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (19 lines × 2) asyncgit/src/sync/rebase.rs:89— asyncgit/src/sync/rebase.rs:89-107 | asyncgit/src/sync/rebase.rs:126-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/sync/rebase.rs:89` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) asyncgit/src/sync/sign.rs:274— asyncgit/src/sync/sign.rs:274-291 | asyncgit/src/sync/sign.rs:362-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/sync/sign.rs:274` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `asyncgit/src/sync/sign.rs:359` calls `arg` and `asyncgit/src/sync/sign.rs:272` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) asyncgit/src/blame.rs:110— asyncgit/src/blame.rs:110-127 | asyncgit/src/diff.rs:126-143 — before extracting anything, compare `asyncgit/src/blame.rs` and `asyncgit/src/diff.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/blame.rs:110` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `params` to `BlameParams` in one and `DiffParams` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) src/components/status_tree.rs:255— src/components/status_tree.rs:255-269 | REDACTED:92-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/components/status_tree.rs:255` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) src/popups/branchlist.rs:655— src/popups/branchlist.rs:655-669 | src/popups/remotelist.rs:295-309 — before extracting anything, compare `src/popups/branchlist.rs` and `src/popups/remotelist.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/branchlist.rs:655` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) src/popups/checkout_option.rs:129— src/popups/checkout_option.rs:129-142 | src/popups/options.rs:259-272 | src/popups/reset.rs:159-172 — before extracting anything, compare `src/popups/checkout_option.rs` and `src/popups/reset.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/checkout_option.rs:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) src/popups/branchlist.rs:455— src/popups/branchlist.rs:455-468 | src/popups/remotelist.rs:421-434 | src/popups/submodules.rs:319-332 — before extracting anything, compare `src/popups/branchlist.rs` and `src/popups/remotelist.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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) asyncgit/src/pull.rs:104— asyncgit/src/pull.rs:104-117 | asyncgit/src/push.rs:115-128 — before extracting anything, compare `asyncgit/src/pull.rs` and `asyncgit/src/push.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/pull.rs:104` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) src/popups/create_remote.rs:58— src/popups/create_remote.rs:58-71 | src/popups/rename_remote.rs:43-56 — before extracting anything, compare `src/popups/create_remote.rs` and `src/popups/rename_remote.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/create_remote.rs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) asyncgit/src/branches.rs:37— asyncgit/src/branches.rs:37-47 | asyncgit/src/filter_commits.rs:65-75 | asyncgit/src/treefiles.rs:42-52 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 3) src/popups/create_remote.rs:191— src/popups/create_remote.rs:191-202 | src/popups/rename_remote.rs:153-163 | src/popups/update_remote_url.rs:130-140 — before extracting anything, compare `src/popups/create_remote.rs` and `src/popups/rename_remote.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/create_remote.rs:191` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) src/popups/pull.rs:208— src/popups/pull.rs:208-216 | src/popups/push.rs:257-265 | src/popups/push_tags.rs:183-191 — before extracting anything, compare `src/popups/pull.rs` and `src/popups/push.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/pull.rs:208` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) asyncgit/src/pull.rs:45— asyncgit/src/pull.rs:45-53 | asyncgit/src/push.rs:52-60 | asyncgit/src/push_tags.rs:43-51 — before extracting anything, compare `asyncgit/src/pull.rs` and `asyncgit/src/push.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/pull.rs:45` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) git2-testing/src/lib.rs:13— git2-testing/src/lib.rs:13-17 | git2-testing/src/lib.rs:35-39 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `git2-testing/src/lib.rs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) src/components/diff.rs:402— src/components/diff.rs:402-406 | src/components/diff.rs:407-411 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/components/diff.rs:402` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Status::event (cyclomatic 35) src/tabs/status.rs:815— Status::event has cyclomatic complexity 35 (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.
DiffComponent::event (cyclomatic 30) src/components/diff.rs:831— DiffComponent::event has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BranchListPopup::event (cyclomatic 27) src/popups/branchlist.rs:123— BranchListPopup::event 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.
asyncgit::sync::staging::apply_selection (cyclomatic 24) asyncgit/src/sync/staging/mod.rs:77— asyncgit::sync::staging::apply_selection has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
RevisionFilesComponent::event (cyclomatic 20) src/components/revision_files.rs:471— RevisionFilesComponent::event has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FileRevlogPopup::event (cyclomatic 20) src/popups/file_revlog.rs:492— FileRevlogPopup::event has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
StatusTreeComponent::event (cyclomatic 19) src/components/status_tree.rs:474— StatusTreeComponent::event has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BlameFilePopup::event (cyclomatic 18) REDACTED:252— BlameFilePopup::event has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SubmodulesListPopup::event (cyclomatic 18) src/popups/submodules.rs:146— SubmodulesListPopup::event has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TagListPopup::event (cyclomatic 18) REDACTED:185— TagListPopup::event has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CommitList::get_entry_to_add (cyclomatic 16) src/components/commitlist.rs:443— CommitList::get_entry_to_add 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.
GotoLinePopup::event (cyclomatic 16) src/popups/goto_line.rs:89— GotoLinePopup::event 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.
WordWrapper::next_line (cyclomatic 16) src/ui/reflow.rs:42— WordWrapper::next_line 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.
GotoLinePopup::event (cognitive 36) src/popups/goto_line.rs:89— GotoLinePopup::event has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (33 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FileRevlogPopup::event (cognitive 33) src/popups/file_revlog.rs:492— FileRevlogPopup::event has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (30 pts), boolean chains 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BranchListPopup::event (cognitive 32) src/popups/branchlist.rs:123— BranchListPopup::event has cognitive complexity 32 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 8 (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.
SubmodulesListPopup::event (cognitive 27) src/popups/submodules.rs:146— SubmodulesListPopup::event has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (27 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.
WordWrapper::next_line (cognitive 27) src/ui/reflow.rs:42— WordWrapper::next_line has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CommitList::get_entry_to_add (cognitive 25) src/components/commitlist.rs:443— CommitList::get_entry_to_add has cognitive complexity 25 (threshold 15). Drivers by points: if/else 22 (23 pts), boolean chains 2 (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.
InspectCommitPopup::event (cognitive 24) src/popups/inspect_commit.rs:144— InspectCommitPopup::event has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
LineTruncator::next_line (cognitive 24) src/ui/reflow.rs:173— LineTruncator::next_line has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (20 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.
Input::input_loop (cognitive 23) src/input.rs:102— Input::input_loop has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SyntaxTextComponent::update (cognitive 21) src/components/syntax_text.rs:62— SyntaxTextComponent::update has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (19 pts), match/switch 1 (2 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TagListPopup::event (cognitive 21) REDACTED:185— TagListPopup::event has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ChangesComponent::event (cognitive 19) src/components/changes.rs:241— ChangesComponent::event has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 3 (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.
CompareCommitsPopup::event (cognitive 19) src/popups/compare_commits.rs:108— CompareCommitsPopup::event has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 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.
StatefulParagraph::render (cognitive 19) src/ui/stateful_paragraph.rs:106— StatefulParagraph::render has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CredComponent::event (cognitive 17) src/components/cred.rs:98— CredComponent::event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StashMsgPopup::event (cognitive 17) src/popups/stashmsg.rs:54— StashMsgPopup::event has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (4 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TextInputComponent::event (cognitive 16) src/components/textinput.rs:676— TextInputComponent::event has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Gitui::run_main_loop (cognitive 16) src/gitui.rs:76— Gitui::run_main_loop has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling: queue.rs ↔ strings.rs src/queue.rs:1— `src/queue.rs` and `src/strings.rs` change together 73% of the time (45 of the 62 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 45 shared commits counted here, the most recent 3 are `3082396b` Support choosing checkout branch method when status is not empty (#2494); `2ab4143d` Add Go to line feature for the blame view (#2262); `d4f9400e` Remotes popup (#2350) — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) src/popups/branchlist.rs:258— src/popups/branchlist.rs:258-291 | src/popups/submodules.rs:146-225 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) src/popups/commit.rs:116— src/popups/commit.rs:116-145 | src/popups/create_branch.rs:158-187 | src/popups/create_remote.rs:137-168 | src/popups/rename_branch.rs:176-205 | src/popups/rename_remote.rs:118-146 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (87 corresponding lines) · ×1
Edited copy of a member (87 corresponding lines) REDACTED:255— REDACTED:255-343 | REDACTED:185-271 — These two members are one piece of code written twice and then edited apart: 87 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (52 corresponding lines) · ×1
Edited copy of a member (52 corresponding lines) asyncgit/src/sync/sign.rs:262— asyncgit/src/sync/sign.rs:262-313 | asyncgit/src/sync/sign.rs:340-395 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (54 corresponding lines) · ×1
Edited copy of a member (54 corresponding lines) asyncgit/src/blame.rs:84— asyncgit/src/blame.rs:84-137 | asyncgit/src/diff.rs:100-153 — These two members are one piece of code written twice and then edited apart: 54 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 46+ corresponding lines) · ×1
Edited copies of one member (3 members, 46+ corresponding lines) asyncgit/src/pull.rs:74— asyncgit/src/pull.rs:74-123 | asyncgit/src/push.rs:81-134 | asyncgit/src/push_tags.rs:72-117 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 46 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 37+ corresponding lines) · ×1
Edited copies of one member (3 members, 37+ corresponding lines) src/popups/branchlist.rs:60— src/popups/branchlist.rs:60-102 | src/popups/remotelist.rs:41-77 | src/popups/submodules.rs:47-97 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 37 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×1
Edited copy of a member (36 corresponding lines) src/ui/scrollbar.rs:40— src/ui/scrollbar.rs:40-75 | src/ui/scrollbar.rs:77-117 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) filetreelist/src/filetreeitems.rs:279— filetreelist/src/filetreeitems.rs:279-324 | REDACTED:417-456 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×1
Edited copy of a member (29 corresponding lines) filetreelist/src/filetreeitems.rs:199— filetreelist/src/filetreeitems.rs:199-239 | filetreelist/src/filetreeitems.rs:244-272 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) src/popups/create_branch.rs:59— src/popups/create_branch.rs:59-91 | src/popups/rename_branch.rs:59-91 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) src/popups/compare_commits.rs:237— src/popups/compare_commits.rs:237-267 | src/popups/file_revlog.rs:159-194 | src/popups/inspect_commit.rs:267-299 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×1
Edited copy of a member (32 corresponding lines) src/popups/compare_commits.rs:75— src/popups/compare_commits.rs:75-106 | src/popups/inspect_commit.rs:103-142 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 27+ corresponding lines) · ×1
Edited copies of one member (3 members, 27+ corresponding lines) src/popups/checkout_option.rs:128— src/popups/checkout_option.rs:128-154 | src/popups/options.rs:258-284 | src/popups/reset.rs:158-184 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 29+ corresponding lines) · ×1
Edited copies of one member (3 members, 29+ corresponding lines) src/popups/branchlist.rs:641— src/popups/branchlist.rs:641-669 | src/popups/remotelist.rs:281-309 | src/popups/submodules.rs:471-499 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 29 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) asyncgit/src/sync/rebase.rs:84— asyncgit/src/sync/rebase.rs:84-107 | asyncgit/src/sync/rebase.rs:112-144 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) src/popups/branchlist.rs:432— src/popups/branchlist.rs:432-453 | src/popups/remotelist.rs:393-414 | src/popups/submodules.rs:297-317 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 23+ corresponding lines) · ×1
Edited copies of one member (3 members, 23+ corresponding lines) src/popups/checkout_option.rs:198— src/popups/checkout_option.rs:198-224 | src/popups/options.rs:320-350 | src/popups/reset.rs:228-250 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) filetreelist/src/filetreeitems.rs:129— filetreelist/src/filetreeitems.rs:129-154 | filetreelist/src/filetreeitems.rs:156-188 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 20+ corresponding lines) · ×1
Edited copies of one member (4 members, 20+ corresponding lines) src/popups/fetch.rs:172— src/popups/fetch.rs:172-191 | src/popups/pull.rs:259-278 | src/popups/push.rs:312-338 | src/popups/push_tags.rs:234-259 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) src/popups/fuzzy_find.rs:339— src/popups/fuzzy_find.rs:339-367 | src/popups/msg.rs:135-154 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) src/popups/fetch.rs:62— src/popups/fetch.rs:62-80 | src/popups/push_tags.rs:65-81 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 14+ corresponding lines) · ×1
Edited copies of one member (5 members, 14+ corresponding lines) asyncgit/src/branches.rs:57— asyncgit/src/branches.rs:57-76 | asyncgit/src/fetch_job.rs:48-68 | asyncgit/src/filter_commits.rs:186-199 | asyncgit/src/remote_tags.rs:65-87 | asyncgit/src/treefiles.rs:62-80 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) asyncgit/src/sync/commits_info.rs:201— asyncgit/src/sync/commits_info.rs:201-212 | asyncgit/src/sync/commits_info.rs:219-230 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) src/popups/create_branch.rs:110— src/popups/create_branch.rs:110-124 | src/popups/rename_branch.rs:110-125 | src/popups/stashmsg.rs:124-138 | src/popups/tag_commit.rs:126-141 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) src/popups/confirm.rs:55— src/popups/confirm.rs:55-68 | src/popups/msg.rs:115-133 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) src/popups/compare_commits.rs:283— src/popups/compare_commits.rs:283-294 | src/popups/file_revlog.rs:443-458 | src/popups/inspect_commit.rs:317-329 | src/popups/revision_files.rs:72-86 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) filetreelist/src/filetree.rs:288— filetreelist/src/filetree.rs:288-297 | filetreelist/src/filetree.rs:302-317 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 14+ corresponding lines) · ×1
Edited copies of one member (4 members, 14+ corresponding lines) src/popups/create_branch.rs:43— src/popups/create_branch.rs:43-57 | src/popups/rename_branch.rs:43-57 | src/popups/stashmsg.rs:38-52 | src/popups/update_remote_url.rs:43-56 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) src/strings.rs:628— src/strings.rs:628-640 | src/strings.rs:756-768 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) src/ui/scrolllist.rs:67— src/ui/scrolllist.rs:67-75 | src/components/mod.rs:292-301 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) src/keys/symbols.rs:90— src/keys/symbols.rs:90-95 | src/options.rs:146-153 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) asyncgit/src/blame.rs:58— asyncgit/src/blame.rs:58-64 | asyncgit/src/diff.rs:76-80 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) asyncgit/src/pull.rs:68— asyncgit/src/pull.rs:68-71 | asyncgit/src/push.rs:75-78 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (35 lines × 2) REDACTED:260— REDACTED:260-294 | REDACTED:190-224 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:260` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (31 lines × 2) src/popups/checkout_option.rs:163— src/popups/checkout_option.rs:163-193 | src/popups/reset.rs:193-223 — before extracting anything, compare `src/popups/checkout_option.rs` and `src/popups/reset.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (29 lines × 2) src/popups/compare_commits.rs:109— src/popups/compare_commits.rs:109-137 | src/popups/inspect_commit.rs:145-173 — before extracting anything, compare `src/popups/compare_commits.rs` and `src/popups/inspect_commit.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/compare_commits.rs:109` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (26–27 lines × 3) src/popups/branchlist.rs:259— src/popups/branchlist.rs:259-284 | src/popups/remotelist.rs:193-219 | src/popups/submodules.rs:152-177 — before extracting anything, compare `src/popups/branchlist.rs` and `src/popups/remotelist.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/branchlist.rs:259` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (27 lines × 2) asyncgit/src/revlog.rs:240— asyncgit/src/revlog.rs:240-266 | asyncgit/src/revlog.rs:283-309 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/revlog.rs:240` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26 lines × 2) src/popups/compare_commits.rs:42— src/popups/compare_commits.rs:42-67 | src/popups/inspect_commit.rs:70-95 — before extracting anything, compare `src/popups/compare_commits.rs` and `src/popups/inspect_commit.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (23–24 lines × 2) src/popups/compare_commits.rs:245— src/popups/compare_commits.rs:245-267 | src/popups/inspect_commit.rs:276-299 — before extracting anything, compare `src/popups/compare_commits.rs` and `src/popups/inspect_commit.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/compare_commits.rs:245` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) src/popups/compare_commits.rs:76— src/popups/compare_commits.rs:76-98 | src/popups/inspect_commit.rs:104-126 — before extracting anything, compare `src/popups/compare_commits.rs` and `src/popups/inspect_commit.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 148 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/compare_commits.rs:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 3) asyncgit/src/sync/cred.rs:96— asyncgit/src/sync/cred.rs:96-116 | asyncgit/src/sync/cred.rs:126-146 | asyncgit/src/sync/cred.rs:156-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. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/sync/cred.rs:96` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 5) src/popups/commit.rs:127— src/popups/commit.rs:127-145 | src/popups/create_branch.rs:167-186 | src/popups/create_remote.rs:148-167 | src/popups/rename_branch.rs:185-204 | src/popups/rename_remote.rs:126-145 — before extracting anything, compare `src/popups/create_branch.rs` and `src/popups/rename_branch.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/commit.rs:127` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17–20 lines × 2) src/popups/fuzzy_find.rs:282— src/popups/fuzzy_find.rs:282-301 | src/popups/log_search.rs:369-385 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/fuzzy_find.rs:282` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 3) asyncgit/src/pull.rs:75— asyncgit/src/pull.rs:75-93 | asyncgit/src/push.rs:82-100 | asyncgit/src/push_tags.rs:73-91 — before extracting anything, compare `asyncgit/src/pull.rs` and `asyncgit/src/push.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/pull.rs:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `params` to `FetchRequest` in one and `PushRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 3) src/popups/compare_commits.rs:43— src/popups/compare_commits.rs:43-60 | src/popups/file_revlog.rs:464-481 | src/popups/inspect_commit.rs:71-88 — before extracting anything, compare `src/popups/compare_commits.rs` and `src/popups/inspect_commit.rs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 148 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 (17 lines × 4) src/popups/fetch.rs:154— src/popups/fetch.rs:154-170 | src/popups/pull.rs:241-257 | src/popups/push.rs:294-310 | src/popups/push_tags.rs:216-232 — before extracting anything, compare `src/popups/fetch.rs` and `src/popups/pull.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13–16 lines × 2) src/popups/remotelist.rs:42— src/popups/remotelist.rs:42-54 | src/popups/submodules.rs:48-63 — before extracting anything, compare `src/popups/remotelist.rs` and `src/popups/submodules.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/remotelist.rs:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–15 lines × 3) asyncgit/src/blame.rs:90— asyncgit/src/blame.rs:90-101 | asyncgit/src/diff.rs:106-117 | asyncgit/src/status.rs:101-115 — before extracting anything, compare `asyncgit/src/blame.rs` and `asyncgit/src/diff.rs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 95 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `asyncgit/src/blame.rs:90` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 4) src/popups/fetch.rs:132— src/popups/fetch.rs:132-145 | src/popups/pull.rs:219-232 | src/popups/push.rs:272-285 | src/popups/push_tags.rs:194-207 — before extracting anything, compare `src/popups/fetch.rs` and `src/popups/pull.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/fetch.rs:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) src/popups/branchlist.rs:695— src/popups/branchlist.rs:695-707 | src/popups/submodules.rs:111-123 | REDACTED:147-159 — before extracting anything, compare `src/popups/branchlist.rs` and `src/popups/submodules.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/branchlist.rs:695` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 3) src/popups/branchlist.rs:433— src/popups/branchlist.rs:433-444 | src/popups/remotelist.rs:394-405 | src/popups/submodules.rs:298-308 — before extracting anything, compare `src/popups/branchlist.rs` and `src/popups/remotelist.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/branchlist.rs:433` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) REDACTED:139— REDACTED:139-150 | src/popups/file_revlog.rs:389-400 — 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–11 lines × 2) src/app.rs:1203— src/app.rs:1203-1210 | src/popups/branchlist.rs:623-633 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/app.rs:1203` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 4) src/popups/create_branch.rs:28— src/popups/create_branch.rs:28-35 | src/popups/create_remote.rs:44-50 | src/popups/rename_branch.rs:29-35 | src/popups/rename_remote.rs:29-35 — before extracting anything, compare `src/popups/create_branch.rs` and `src/popups/rename_branch.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/popups/create_remote.rs:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `f` to `&mut Frame` in one and `&mut ratatui::Frame` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 4) src/app.rs:1091— src/app.rs:1091-1099 | src/popups/create_remote.rs:194-204 | src/popups/rename_remote.rs:156-165 | src/popups/update_remote_url.rs:133-142 — before extracting anything, compare `src/popups/create_remote.rs` and `src/popups/rename_remote.rs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 65 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/app.rs:1091` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: Callbacks (LCOM4 4) asyncgit/src/sync/remotes/callbacks.rs:18— Callbacks's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Orphaned file src/ui/reflow.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 src/components/status_tree.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 asyncgit/src/sync/diff.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 src/components/revision_files.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 REDACTED: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 filetreelist/src/filetree.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 src/components/commit_details/details.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 asyncgit/src/sync/remotes/push.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 asyncgit/src/sync/remotes/tags.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 src/ui/style.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 src/components/utils/filetree.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 asyncgit/src/sync/stash.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 src/popups/fuzzy_find.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 src/popups/options.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 asyncgit/src/sync/rebase.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 asyncgit/src/sync/reset.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 src/components/changes.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 asyncgit/src/asyncjob/mod.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 src/keys/key_config.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 src/popups/inspect_commit.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 asyncgit/src/sync/branch/merge_rebase.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 src/popups/confirm.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 src/components/syntax_text.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 src/popups/compare_commits.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 src/popups/pull.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.
Duplicated predicate src/components/status_tree.rs:255— `idx_temp < tree_items.len().saturating_sub(2) && tree_items[idx_temp].info.indent` appears character-identically in 2 files — src/components/status_tree.rs, REDACTED. 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 src/popups/push.rs:327— `key_match( e, self.key_config.keys.exit_popup, ) && !self.pending` appears character-identically in 2 files — src/popups/push.rs, src/popups/push_tags.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 src/popups/compare_commits.rs:127— `key_match( e, self.key_config.keys.move_right, ) && self.can_focus_diff()` appears character-identically in 2 files — src/popups/compare_commits.rs, src/popups/inspect_commit.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:276— `key_match( key, self.key_config.keys.shift_down, ) || key_match( key, self.key_config.keys.end, )` appears character-identically in 3 files — REDACTED, src/popups/file_revlog.rs, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:268— `key_match( key, self.key_config.keys.shift_up, ) || key_match( key, self.key_config.keys.home, )` appears character-identically in 3 files — REDACTED, src/popups/file_revlog.rs, REDACTED. 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 src/components/commit_details/details.rs:384— `key_match(e, self.key_config.keys.home) || key_match(e, self.key_config.keys.shift_up)` appears character-identically in 2 files — src/components/commit_details/details.rs, src/components/status_tree.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 src/popups/compare_commits.rs:202— `self.git_diff.is_pending() || self.details.any_work_pending()` appears character-identically in 2 files — src/popups/compare_commits.rs, src/popups/inspect_commit.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 src/popups/fetch.rs:178— `self.input_cred.get_cred().is_complete() || !self.input_cred.is_visible()` appears character-identically in 4 files — src/popups/fetch.rs, src/popups/pull.rs, src/popups/push.rs, src/popups/push_tags.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 src/popups/branchlist.rs:337— `self.is_visible() && ev == AsyncGitNotification::Push` appears character-identically in 2 files — src/popups/branchlist.rs, src/popups/push.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.
D34 · Knowledge Freshness· Most significant orphaned file · ×2
Most significant orphaned file asyncgit/src/sync/branch/mod.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file filetreelist/src/filetreeitems.rs:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: asyncgit/src/revlog.rs, asyncgit/src/sync/tags.rs. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (4 single-owned of 127 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 127 of the 161 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: asyncgit/src/sync/remotes/callbacks.rs, asyncgit/src/push.rs.
No ADRs found src/main.rs:1— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `src/main.rs` makes this repository a deployable product (line 1).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 7 project(s) overshoot their size bounds, lowering Project Cohesion to 4.3/10. The most over is `(repository root)` (26275 LoC, 144 module-visible types across 8 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.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×1
Concentrated knowledge decay — 66 of 127 significant files have no living knowledge, while the repository is still being changed at a low rate (3 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 66 separate risks. Counted over 127 of the 161 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
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.
P3 · Security & performance tooling· Dependabot does not watch github-actions · ×1
Dependabot does not watch github-actions REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
Outdated: anyhow — `anyhow` is locked at 1.0.103 but 1.0.104 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p anyhow` and commit the updated REDACTED.
Outdated: backtrace — `backtrace` is locked at 0.3.76 but 0.3.77 is the current stable release on crates.io, and it already satisfies the `"0.3"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p backtrace` and commit the updated REDACTED.
Outdated: bitflags — `bitflags` is locked at 2.10.0 but 2.13.2 is the current stable release on crates.io, and it already satisfies the `"2.10"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bitflags` and commit the updated REDACTED.
Outdated: bytesize — `bytesize` is locked at 2.3.1 but 2.7.0 is the current stable release on crates.io, and it already satisfies the `"2.3"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p bytesize` and commit the updated REDACTED.
Outdated: chrono — `chrono` is locked at 0.4.44 but 0.4.45 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p chrono` and commit the updated REDACTED.
Outdated: clap — `clap` is locked at 4.5.57 but 4.6.7 is the current stable release on crates.io, and it already satisfies the `"4.5"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p clap` and commit the updated REDACTED.
Outdated: crossbeam-channel — `crossbeam-channel` is locked at 0.5.15 but 0.5.17 is the current stable release on crates.io, and it already satisfies the `"0.5"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p crossbeam-channel` and commit the updated REDACTED.
Outdated: env_logger — `env_logger` is locked at 0.11.9 but 0.11.11 is the current stable release on crates.io, and it already satisfies the `"0.11"` requirement declared in git2-testing/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p env_logger` and commit the updated REDACTED.
Outdated: gh-emoji — `gh-emoji` is locked at 1.0.8 but 1.0.9 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p gh-emoji` and commit the updated REDACTED.
Outdated: indexmap — `indexmap` is locked at 2.13.0 but 2.14.2 is the current stable release on crates.io, and it already satisfies the `"2"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p indexmap` and commit the updated REDACTED.
Outdated: log — `log` is locked at 0.4.29 but 0.4.35 is the current stable release on crates.io, and it already satisfies the `"0.4"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p log` and commit the updated REDACTED.
Outdated: notify — `notify` is locked at 8.2.0 but 8.2.2 is the current stable release on crates.io, and it already satisfies the `"8"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p notify` and commit the updated REDACTED.
Outdated: once_cell — `once_cell` is locked at 1.21.3 but 1.21.4 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p once_cell` and commit the updated REDACTED.
Outdated: openssl-sys — `openssl-sys` is locked at 0.9.111 but 0.9.118 is the current stable release on crates.io, and it already satisfies the `"0.9"` requirement declared in asyncgit/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p openssl-sys` and commit the updated REDACTED.
Outdated: ratatui — `ratatui` is locked at 0.30.0 but 0.30.2 is the current stable release on crates.io, and it already satisfies the `"0.30"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ratatui` and commit the updated REDACTED.
Outdated: rayon — `rayon` is locked at 1.11.0 but 1.12.0 is the current stable release on crates.io, and it already satisfies the `"1.11"` requirement declared in asyncgit/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rayon` and commit the updated REDACTED.
Outdated: ron — `ron` is locked at 0.12.0 but 0.12.3 is the current stable release on crates.io, and it already satisfies the `"0.12"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p ron` and commit the updated REDACTED.
Outdated: serde — `serde` is locked at 1.0.228 but 1.0.229 is the current stable release on crates.io, and it already satisfies the `"1.0"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p serde` and commit the updated REDACTED.
Outdated: shellexpand — `shellexpand` is locked at 3.1.1 but 3.1.2 is the current stable release on crates.io, and it already satisfies the `"3.1"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p shellexpand` and commit the updated REDACTED.
Outdated: thiserror — `thiserror` is locked at 2.0.18 but 2.0.21 is the current stable release on crates.io, and it already satisfies the `"2.0"` requirement declared in asyncgit/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p thiserror` and commit the updated REDACTED.
Outdated: unicode-segmentation — `unicode-segmentation` is locked at 1.12.0 but 1.13.3 is the current stable release on crates.io, and it already satisfies the `"1.12"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p unicode-segmentation` and commit the updated REDACTED.
Outdated: unicode-width — `unicode-width` is locked at 0.2.0 but 0.2.3 is the current stable release on crates.io, and it already satisfies the `"0.2"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p unicode-width` and commit the updated REDACTED.
Outdated: url — `url` is locked at 2.5.4 but 2.5.8 is the current stable release on crates.io, and it already satisfies the `"2.5"` requirement declared in asyncgit/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p url` and commit the updated REDACTED.
Outdated: which — `which` is locked at 8.0.0 but 8.0.6 is the current stable release on crates.io, and it already satisfies the `"8.0"` requirement declared in Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p which` 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 01a1d88a-1d93-78ce-a789-d619407bbed9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 49 · Warnings: 400 · Recommendations: 86 · Info: 24 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 05:31 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.