Public report of tailcallhq/forgecode, 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, 17:18 UTC · Survey ID cd_0657cae73c324b4a81b4018696668c46
tailcallhq/forgecode
Measured 14 November 2026, 17:16 UTC, at code version a22b492
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
No change since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 116,561 lines of product code in 25 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Accessibility, 32
Findings by how serious they are
68 critical324 serious110 minor
21 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, 17:16 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 ▸
52of 52 dimensions measured by tools.
461of 502 findings point to an exact file and line, so you can open each one in the code. The other 41 concern the repository as a whole, such as missing documentation.
52dimensions across 9 lenses, read from 116,561 lines of product code in 25 projects.
tailcallhq/forgecode falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 48 out of 100 and is rated Weak, and 64 of its 68 critical findings are security problems.
Accessibility, at 32, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 13 points. Structuring the pages comes next, worth about 8 points. Raising Accessibility to 70 would lift the score to about 61.
Thirty-four pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Seventeen secrets can leak from the build pipeline, and seven known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. Correcting the flagged pipeline settings would fix the three 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 two parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.
The product code is 116,561 lines, about €110,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.
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: 30 findings
These 30 critical or serious findings were in the previous survey, on 27 October 2026, and are gone from this one.
Code Duplication · Near-duplicate member pair (33 shared lines) crates/forge_repo/src/provider/openai.rs
A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €110,000 · Estimate
Cost to rebuild
€36,000 to €180,000, for 603 to 1,913 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 116,561 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
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Raises the score by about 8 points · Medium effort · Page structure
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
Raises the score by about 3 points · Low effort · ADR Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €110,000 to build again, about 0.7 person-years of work. Its weakest lens is Accessibility, at 32 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1. Of all the actions in this report, it raises the score most for the work it takes: about 13 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
393 modules, with 824 dependencies between them. 5 loops run through 30 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 353 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.
forge_domain.auth.auth_context uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.auth.auth_context, while a change to forge_domain.auth.auth_context can't break forge_domain.auth.new_types.
Position
Below the diagonal: forge_domain.auth.auth_context uses a module listed above it, which is the healthy direction.
forge_domain.event uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.event, while a change to forge_domain.event can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_domain.event uses a module listed above it, which is the healthy direction.
forge_domain.node uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.node, while a change to forge_domain.node can't break forge_domain.auth.new_types.
Position
Below the diagonal: forge_domain.node uses a module listed above it, which is the healthy direction.
forge_domain.tools.catalog uses forge_domain.env, so a change to forge_domain.env can break forge_domain.tools.catalog, while a change to forge_domain.tools.catalog can't break forge_domain.env.
Position
Below the diagonal: forge_domain.tools.catalog uses a module listed above it, which is the healthy direction.
forge_domain.tools.catalog uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.tools.catalog, while a change to forge_domain.tools.catalog can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_domain.tools.catalog uses a module listed above it, which is the healthy direction.
12→14 forge_domain.tools.catalog uses forge_domain.tools.call.tool_callpart of a loop✕
Connections
2 pairs of types, where a type in forge_domain.tools.catalog uses a type in forge_domain.tools.call.tool_call.
forge_domain.tools.catalog uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.tools.catalog, while a change to forge_domain.tools.catalog can't break forge_domain.tools.call.tool_call.
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.
forge_domain.auth.credentials uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.auth.credentials, while a change to forge_domain.auth.credentials can't break forge_domain.auth.new_types.
Position
Below the diagonal: forge_domain.auth.credentials uses a module listed above it, which is the healthy direction.
forge_domain.auth.credentials uses forge_domain.node, so a change to forge_domain.node can break forge_domain.auth.credentials, while a change to forge_domain.auth.credentials can't break forge_domain.node.
Position
Below the diagonal: forge_domain.auth.credentials uses a module listed above it, which is the healthy direction.
13→15 forge_domain.auth.credentials uses forge_domain.providerpart of a loop✕
Connections
1 pair of types, where a type in forge_domain.auth.credentials uses a type in forge_domain.provider.
forge_domain.auth.credentials uses forge_domain.provider, so a change to forge_domain.provider can break forge_domain.auth.credentials, while a change to forge_domain.auth.credentials can't break forge_domain.provider.
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.
forge_domain.tools.call.tool_call uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.tools.call.tool_call, while a change to forge_domain.tools.call.tool_call can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_domain.tools.call.tool_call uses a module listed above it, which is the healthy direction.
forge_domain.tools.call.tool_call uses forge_domain.tools.catalog, so a change to forge_domain.tools.catalog can break forge_domain.tools.call.tool_call, while a change to forge_domain.tools.call.tool_call can't break forge_domain.tools.catalog.
Position
Below the diagonal: forge_domain.tools.call.tool_call uses a module listed above it, which is the healthy direction.
forge_domain.provider uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_domain.provider, while a change to forge_domain.provider can't break forge_domain.auth.auth_method.
Position
Below the diagonal: forge_domain.provider uses a module listed above it, which is the healthy direction.
forge_domain.provider uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.provider, while a change to forge_domain.provider can't break forge_domain.auth.new_types.
Position
Below the diagonal: forge_domain.provider uses a module listed above it, which is the healthy direction.
forge_domain.provider uses forge_domain.model, so a change to forge_domain.model can break forge_domain.provider, while a change to forge_domain.provider can't break forge_domain.model.
Position
Below the diagonal: forge_domain.provider uses a module listed above it, which is the healthy direction.
forge_domain.provider uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_domain.provider, while a change to forge_domain.provider can't break forge_domain.auth.credentials.
Position
Below the diagonal: forge_domain.provider uses a module listed above it, which is the healthy direction.
forge_domain.tools.result uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.tools.result, while a change to forge_domain.tools.result can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_domain.tools.result uses a module listed above it, which is the healthy direction.
forge_domain.tools.result uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.tools.result, while a change to forge_domain.tools.result can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_domain.tools.result uses a module listed above it, which is the healthy direction.
16→25 forge_domain.tools.result uses forge_domain.conversationpart of a loop✕
Connections
1 pair of types, where a type in forge_domain.tools.result uses a type in forge_domain.conversation.
forge_domain.tools.result uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_domain.tools.result, while a change to forge_domain.tools.result can't break forge_domain.conversation.
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.
forge_app.infra uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.auth.auth_method.
Position
Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
forge_app.infra uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.auth.new_types.
Position
Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
forge_app.infra uses forge_domain.env, so a change to forge_domain.env can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.env.
Position
Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
forge_app.infra uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.mcp.
Position
Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
forge_app.infra uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
forge_app.infra uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.auth.auth_context.
Position
Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
forge_app.infra uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.auth.credentials.
Position
Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
forge_app.infra uses forge_domain.provider, so a change to forge_domain.provider can break forge_app.infra, while a change to forge_app.infra can't break forge_domain.provider.
Position
Below the diagonal: forge_app.infra uses a module listed above it, which is the healthy direction.
forge_domain.agent uses forge_config.config, so a change to forge_config.config can break forge_domain.agent, while a change to forge_domain.agent can't break forge_config.config.
Position
Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
forge_domain.agent uses forge_domain.model, so a change to forge_domain.model can break forge_domain.agent, while a change to forge_domain.agent can't break forge_domain.model.
Position
Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
forge_domain.agent uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_domain.agent, while a change to forge_domain.agent can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
forge_domain.agent uses forge_domain.provider, so a change to forge_domain.provider can break forge_domain.agent, while a change to forge_domain.agent can't break forge_domain.provider.
Position
Below the diagonal: forge_domain.agent uses a module listed above it, which is the healthy direction.
forge_domain.hook uses forge_domain.model, so a change to forge_domain.model can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.model.
Position
Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
forge_domain.hook uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
forge_domain.hook uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.tools.result.
Position
Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
forge_domain.hook uses forge_domain.agent, so a change to forge_domain.agent can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.agent.
Position
Below the diagonal: forge_domain.hook uses a module listed above it, which is the healthy direction.
19→22 forge_domain.hook uses forge_domain.messagepart of a loop✕
Connections
1 pair of types, where a type in forge_domain.hook uses a type in forge_domain.message.
forge_domain.hook uses forge_domain.message, so a change to forge_domain.message can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.message.
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.
19→25 forge_domain.hook uses forge_domain.conversationpart of a loop✕
Connections
4 pairs of types, where a type in forge_domain.hook uses a type in forge_domain.conversation.
forge_domain.hook uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_domain.hook, while a change to forge_domain.hook can't break forge_domain.conversation.
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.
forge_infra.forge_infra uses forge_config.config, so a change to forge_config.config can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_config.config.
Position
Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
forge_infra.forge_infra uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.auth.auth_method.
Position
Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
forge_infra.forge_infra uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.auth.new_types.
Position
Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
forge_infra.forge_infra uses forge_domain.env, so a change to forge_domain.env can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.env.
Position
Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
forge_infra.forge_infra uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.mcp.
Position
Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
forge_infra.forge_infra uses forge_domain.provider, so a change to forge_domain.provider can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_domain.provider.
Position
Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
forge_infra.forge_infra uses forge_app.infra, so a change to forge_app.infra can break forge_infra.forge_infra, while a change to forge_infra.forge_infra can't break forge_app.infra.
Position
Below the diagonal: forge_infra.forge_infra uses a module listed above it, which is the healthy direction.
forge_repo.agent_definition uses forge_domain.model, so a change to forge_domain.model can break forge_repo.agent_definition, while a change to forge_repo.agent_definition can't break forge_domain.model.
Position
Below the diagonal: forge_repo.agent_definition uses a module listed above it, which is the healthy direction.
forge_repo.agent_definition uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_repo.agent_definition, while a change to forge_repo.agent_definition can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_repo.agent_definition uses a module listed above it, which is the healthy direction.
forge_repo.agent_definition uses forge_domain.provider, so a change to forge_domain.provider can break forge_repo.agent_definition, while a change to forge_repo.agent_definition can't break forge_domain.provider.
Position
Below the diagonal: forge_repo.agent_definition uses a module listed above it, which is the healthy direction.
forge_repo.agent_definition uses forge_domain.agent, so a change to forge_domain.agent can break forge_repo.agent_definition, while a change to forge_repo.agent_definition can't break forge_domain.agent.
Position
Below the diagonal: forge_repo.agent_definition uses a module listed above it, which is the healthy direction.
forge_domain.message uses forge_domain.event, so a change to forge_domain.event can break forge_domain.message, while a change to forge_domain.message can't break forge_domain.event.
Position
Below the diagonal: forge_domain.message uses a module listed above it, which is the healthy direction.
forge_domain.message uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.message, while a change to forge_domain.message can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_domain.message uses a module listed above it, which is the healthy direction.
forge_domain.message uses forge_domain.hook, so a change to forge_domain.hook can break forge_domain.message, while a change to forge_domain.message can't break forge_domain.hook.
Position
Below the diagonal: forge_domain.message uses a module listed above it, which is the healthy direction.
22→23 forge_domain.message uses forge_domain.contextpart of a loop✕
Connections
1 pair of types, where a type in forge_domain.message uses a type in forge_domain.context.
forge_domain.message uses forge_domain.context, so a change to forge_domain.context can break forge_domain.message, while a change to forge_domain.message can't break forge_domain.context.
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.
forge_domain.context uses forge_domain.model, so a change to forge_domain.model can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.model.
Position
Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
forge_domain.context uses forge_domain.event, so a change to forge_domain.event can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.event.
Position
Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
forge_domain.context uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
forge_domain.context uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.tools.result.
Position
Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
forge_domain.context uses forge_domain.agent, so a change to forge_domain.agent can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.agent.
Position
Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
forge_domain.context uses forge_domain.message, so a change to forge_domain.message can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.message.
Position
Below the diagonal: forge_domain.context uses a module listed above it, which is the healthy direction.
23→25 forge_domain.context uses forge_domain.conversationpart of a loop✕
Connections
1 pair of types, where a type in forge_domain.context uses a type in forge_domain.conversation.
forge_domain.context uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_domain.context, while a change to forge_domain.context can't break forge_domain.conversation.
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.
forge_app.dto.anthropic.request uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.dto.anthropic.request, while a change to forge_app.dto.anthropic.request can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_app.dto.anthropic.request uses a module listed above it, which is the healthy direction.
forge_app.dto.anthropic.request uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_app.dto.anthropic.request, while a change to forge_app.dto.anthropic.request can't break forge_domain.tools.result.
Position
Below the diagonal: forge_app.dto.anthropic.request uses a module listed above it, which is the healthy direction.
forge_app.dto.anthropic.request uses forge_domain.context, so a change to forge_domain.context can break forge_app.dto.anthropic.request, while a change to forge_app.dto.anthropic.request can't break forge_domain.context.
Position
Below the diagonal: forge_app.dto.anthropic.request uses a module listed above it, which is the healthy direction.
forge_domain.conversation uses forge_domain.message, so a change to forge_domain.message can break forge_domain.conversation, while a change to forge_domain.conversation can't break forge_domain.message.
Position
Below the diagonal: forge_domain.conversation uses a module listed above it, which is the healthy direction.
forge_domain.conversation uses forge_domain.context, so a change to forge_domain.context can break forge_domain.conversation, while a change to forge_domain.conversation can't break forge_domain.context.
Position
Below the diagonal: forge_domain.conversation uses a module listed above it, which is the healthy direction.
forge_api.api uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_api.api, while a change to forge_api.api can't break forge_domain.auth.auth_method.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
forge_api.api uses forge_domain.env, so a change to forge_domain.env can break forge_api.api, while a change to forge_api.api can't break forge_domain.env.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in forge_api.api uses a type in forge_domain.mcp.
The types involved
forge_api.api.API → forge_domain.mcp.McpConfig
forge_api.api.API → forge_domain.mcp.Scope
Direction
forge_api.api uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_api.api, while a change to forge_api.api can't break forge_domain.mcp.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in forge_api.api uses a type in forge_domain.model.
The types involved
forge_api.api.API → forge_domain.model.ModelId
Direction
forge_api.api uses forge_domain.model, so a change to forge_domain.model can break forge_api.api, while a change to forge_api.api can't break forge_domain.model.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
forge_api.api uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_api.api, while a change to forge_api.api can't break forge_domain.auth.auth_context.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in forge_api.api uses a type in forge_domain.event.
The types involved
forge_api.api.API → forge_domain.event.UserPrompt
Direction
forge_api.api uses forge_domain.event, so a change to forge_domain.event can break forge_api.api, while a change to forge_api.api can't break forge_domain.event.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
forge_api.api uses forge_domain.node, so a change to forge_domain.node can break forge_api.api, while a change to forge_api.api can't break forge_domain.node.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
forge_api.api uses forge_domain.provider, so a change to forge_domain.provider can break forge_api.api, while a change to forge_api.api can't break forge_domain.provider.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in forge_api.api uses a type in forge_domain.agent.
The types involved
forge_api.api.API → forge_domain.agent.AgentId
Direction
forge_api.api uses forge_domain.agent, so a change to forge_domain.agent can break forge_api.api, while a change to forge_api.api can't break forge_domain.agent.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
forge_api.api uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_api.api, while a change to forge_api.api can't break forge_domain.conversation.
Position
Below the diagonal: forge_api.api uses a module listed above it, which is the healthy direction.
forge_app.dto.google.response uses forge_domain.message, so a change to forge_domain.message can break forge_app.dto.google.response, while a change to forge_app.dto.google.response can't break forge_domain.message.
Position
Below the diagonal: forge_app.dto.google.response uses a module listed above it, which is the healthy direction.
forge_app.dto.google.response uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.dto.google.response, while a change to forge_app.dto.google.response can't break forge_app.dto.anthropic.request.
Position
Below the diagonal: forge_app.dto.google.response uses a module listed above it, which is the healthy direction.
27→32 forge_app.dto.google.response uses forge_app.dto.anthropic.responsepart of a loop✕
Connections
2 pairs of types, where a type in forge_app.dto.google.response uses a type in forge_app.dto.anthropic.response.
forge_app.dto.google.response uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_app.dto.google.response, while a change to forge_app.dto.google.response can't break forge_app.dto.anthropic.response.
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.
forge_app.dto.openai.request uses forge_domain.model, so a change to forge_domain.model can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.model.
Position
Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
forge_app.dto.openai.request uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
forge_app.dto.openai.request uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
forge_app.dto.openai.request uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.tools.result.
Position
Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
forge_app.dto.openai.request uses forge_domain.context, so a change to forge_domain.context can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_domain.context.
Position
Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
forge_app.dto.openai.request uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.dto.openai.request, while a change to forge_app.dto.openai.request can't break forge_app.dto.anthropic.request.
Position
Below the diagonal: forge_app.dto.openai.request uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_app.services, while a change to forge_app.services can't break forge_domain.auth.auth_method.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.env, so a change to forge_domain.env can break forge_app.services, while a change to forge_app.services can't break forge_domain.env.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_app.services, while a change to forge_app.services can't break forge_domain.mcp.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.model, so a change to forge_domain.model can break forge_app.services, while a change to forge_app.services can't break forge_domain.model.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_app.services, while a change to forge_app.services can't break forge_domain.auth.auth_context.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.node, so a change to forge_domain.node can break forge_app.services, while a change to forge_app.services can't break forge_domain.node.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.tools.catalog, so a change to forge_domain.tools.catalog can break forge_app.services, while a change to forge_app.services can't break forge_domain.tools.catalog.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_app.services, while a change to forge_app.services can't break forge_domain.auth.credentials.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.services, while a change to forge_app.services can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.provider, so a change to forge_domain.provider can break forge_app.services, while a change to forge_app.services can't break forge_domain.provider.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_app.infra, so a change to forge_app.infra can break forge_app.services, while a change to forge_app.services can't break forge_app.infra.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.agent, so a change to forge_domain.agent can break forge_app.services, while a change to forge_app.services can't break forge_domain.agent.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.context, so a change to forge_domain.context can break forge_app.services, while a change to forge_app.services can't break forge_domain.context.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.services, while a change to forge_app.services can't break forge_app.dto.anthropic.request.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_app.services uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_app.services, while a change to forge_app.services can't break forge_domain.conversation.
Position
Below the diagonal: forge_app.services uses a module listed above it, which is the healthy direction.
forge_domain.repo uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.auth.new_types.
Position
Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
forge_domain.repo uses forge_domain.model, so a change to forge_domain.model can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.model.
Position
Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
forge_domain.repo uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.auth.credentials.
Position
Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
forge_domain.repo uses forge_domain.provider, so a change to forge_domain.provider can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.provider.
Position
Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
forge_domain.repo uses forge_domain.context, so a change to forge_domain.context can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.context.
Position
Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
forge_domain.repo uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_domain.repo, while a change to forge_domain.repo can't break forge_domain.conversation.
Position
Below the diagonal: forge_domain.repo uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_config.config, so a change to forge_config.config can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_config.config.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.auth.auth_method.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.env, so a change to forge_domain.env can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.env.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.mcp.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.model, so a change to forge_domain.model can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.model.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.auth.auth_context.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.event, so a change to forge_domain.event can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.event.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.node, so a change to forge_domain.node can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.node.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.provider, so a change to forge_domain.provider can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.provider.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.agent, so a change to forge_domain.agent can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.agent.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_api.forge_api uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_domain.conversation.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in forge_api.forge_api uses a type in forge_api.api.
The types involved
forge_api.forge_api.ForgeAPI → forge_api.api.API
Direction
forge_api.forge_api uses forge_api.api, so a change to forge_api.api can break forge_api.forge_api, while a change to forge_api.forge_api can't break forge_api.api.
Position
Below the diagonal: forge_api.forge_api uses a module listed above it, which is the healthy direction.
forge_app.dto.anthropic.response uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.dto.anthropic.response, while a change to forge_app.dto.anthropic.response can't break forge_app.dto.anthropic.request.
Position
Below the diagonal: forge_app.dto.anthropic.response uses a module listed above it, which is the healthy direction.
forge_app.dto.anthropic.response uses forge_app.dto.google.response, so a change to forge_app.dto.google.response can break forge_app.dto.anthropic.response, while a change to forge_app.dto.anthropic.response can't break forge_app.dto.google.response.
Position
Below the diagonal: forge_app.dto.anthropic.response uses a module listed above it, which is the healthy direction.
forge_repo.provider.chat uses forge_domain.model, so a change to forge_domain.model can break forge_repo.provider.chat, while a change to forge_repo.provider.chat can't break forge_domain.model.
Position
Below the diagonal: forge_repo.provider.chat uses a module listed above it, which is the healthy direction.
forge_repo.provider.chat uses forge_domain.provider, so a change to forge_domain.provider can break forge_repo.provider.chat, while a change to forge_repo.provider.chat can't break forge_domain.provider.
Position
Below the diagonal: forge_repo.provider.chat uses a module listed above it, which is the healthy direction.
forge_repo.provider.chat uses forge_domain.context, so a change to forge_domain.context can break forge_repo.provider.chat, while a change to forge_repo.provider.chat can't break forge_domain.context.
Position
Below the diagonal: forge_repo.provider.chat uses a module listed above it, which is the healthy direction.
forge_repo.provider.chat uses forge_domain.repo, so a change to forge_domain.repo can break forge_repo.provider.chat, while a change to forge_repo.provider.chat can't break forge_domain.repo.
Position
Below the diagonal: forge_repo.provider.chat uses a module listed above it, which is the healthy direction.
forge_services.forge_services uses forge_domain.env, so a change to forge_domain.env can break forge_services.forge_services, while a change to forge_services.forge_services can't break forge_domain.env.
Position
Below the diagonal: forge_services.forge_services uses a module listed above it, which is the healthy direction.
forge_services.forge_services uses forge_app.infra, so a change to forge_app.infra can break forge_services.forge_services, while a change to forge_services.forge_services can't break forge_app.infra.
Position
Below the diagonal: forge_services.forge_services uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in forge_services.forge_services uses a type in forge_app.services. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
forge_services.forge_services uses forge_app.services, so a change to forge_app.services can break forge_services.forge_services, while a change to forge_services.forge_services can't break forge_app.services.
Position
Below the diagonal: forge_services.forge_services uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_config.config, so a change to forge_config.config can break forge_app.orch, while a change to forge_app.orch can't break forge_config.config.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_domain.model, so a change to forge_domain.model can break forge_app.orch, while a change to forge_app.orch can't break forge_domain.model.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.orch, while a change to forge_app.orch can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_domain.agent, so a change to forge_domain.agent can break forge_app.orch, while a change to forge_app.orch can't break forge_domain.agent.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_domain.hook, so a change to forge_domain.hook can break forge_app.orch, while a change to forge_app.orch can't break forge_domain.hook.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_domain.context, so a change to forge_domain.context can break forge_app.orch, while a change to forge_app.orch can't break forge_domain.context.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.orch, while a change to forge_app.orch can't break forge_app.dto.anthropic.request.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_app.orch, while a change to forge_app.orch can't break forge_domain.conversation.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.orch uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_app.orch, while a change to forge_app.orch can't break forge_app.dto.anthropic.response.
Position
Below the diagonal: forge_app.orch uses a module listed above it, which is the healthy direction.
forge_app.tool_registry uses forge_domain.env, so a change to forge_domain.env can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.env.
Position
Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
forge_app.tool_registry uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
forge_app.tool_registry uses forge_domain.tools.catalog, so a change to forge_domain.tools.catalog can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.tools.catalog.
Position
Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
forge_app.tool_registry uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
forge_app.tool_registry uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.tools.result.
Position
Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
forge_app.tool_registry uses forge_domain.agent, so a change to forge_domain.agent can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_domain.agent.
Position
Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
forge_app.tool_registry uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_app.dto.anthropic.request.
Position
Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
forge_app.tool_registry uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_app.tool_registry, while a change to forge_app.tool_registry can't break forge_app.dto.anthropic.response.
Position
Below the diagonal: forge_app.tool_registry uses a module listed above it, which is the healthy direction.
forge_main.info uses forge_config.config, so a change to forge_config.config can break forge_main.info, while a change to forge_main.info can't break forge_config.config.
Position
Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
forge_main.info uses forge_domain.env, so a change to forge_domain.env can break forge_main.info, while a change to forge_main.info can't break forge_domain.env.
Position
Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
forge_main.info uses forge_domain.context, so a change to forge_domain.context can break forge_main.info, while a change to forge_main.info can't break forge_domain.context.
Position
Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
forge_main.info uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_main.info, while a change to forge_main.info can't break forge_domain.conversation.
Position
Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
forge_main.info uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_main.info, while a change to forge_main.info can't break forge_app.dto.anthropic.response.
Position
Below the diagonal: forge_main.info uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_domain.env, so a change to forge_domain.env can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.env.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_domain.model, so a change to forge_domain.model can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.model.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_domain.tools.definition.name, so a change to forge_domain.tools.definition.name can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.tools.definition.name.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_domain.event, so a change to forge_domain.event can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.event.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_domain.tools.call.tool_call, so a change to forge_domain.tools.call.tool_call can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.tools.call.tool_call.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_domain.tools.result, so a change to forge_domain.tools.result can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.tools.result.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_domain.context, so a change to forge_domain.context can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.context.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_app.dto.anthropic.request, so a change to forge_app.dto.anthropic.request can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_app.dto.anthropic.request.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_domain.conversation.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.conversation.conversation_record uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_repo.conversation.conversation_record, while a change to forge_repo.conversation.conversation_record can't break forge_app.dto.anthropic.response.
Position
Below the diagonal: forge_repo.conversation.conversation_record uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.auth.auth_method.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.auth.new_types, so a change to forge_domain.auth.new_types can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.auth.new_types.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.env, so a change to forge_domain.env can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.env.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.mcp.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.model, so a change to forge_domain.model can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.model.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.auth.credentials, so a change to forge_domain.auth.credentials can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.auth.credentials.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.provider, so a change to forge_domain.provider can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.provider.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_app.infra, so a change to forge_app.infra can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_app.infra.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.context, so a change to forge_domain.context can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.context.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.conversation.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_domain.repo, so a change to forge_domain.repo can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_domain.repo.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_repo.forge_repo uses forge_repo.provider.chat, so a change to forge_repo.provider.chat can break forge_repo.forge_repo, while a change to forge_repo.forge_repo can't break forge_repo.provider.chat.
Position
Below the diagonal: forge_repo.forge_repo uses a module listed above it, which is the healthy direction.
forge_main.ui uses forge_config.config, so a change to forge_config.config can break forge_main.ui, while a change to forge_main.ui can't break forge_config.config.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
forge_main.ui uses forge_domain.auth.auth_method, so a change to forge_domain.auth.auth_method can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.auth.auth_method.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
forge_main.ui uses forge_domain.mcp, so a change to forge_domain.mcp can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.mcp.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in forge_main.ui uses a type in forge_domain.model.
The types involved
forge_main.ui.UI → forge_domain.model.ModelId
Direction
forge_main.ui uses forge_domain.model, so a change to forge_domain.model can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.model.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
forge_main.ui uses forge_domain.auth.auth_context, so a change to forge_domain.auth.auth_context can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.auth.auth_context.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in forge_main.ui uses a type in forge_domain.event.
The types involved
forge_main.ui.UI → forge_domain.event.UserPrompt
Direction
forge_main.ui uses forge_domain.event, so a change to forge_domain.event can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.event.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
forge_main.ui uses forge_domain.node, so a change to forge_domain.node can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.node.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
forge_main.ui uses forge_domain.provider, so a change to forge_domain.provider can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.provider.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in forge_main.ui uses a type in forge_domain.agent.
The types involved
forge_main.ui.UI → forge_domain.agent.AgentId
Direction
forge_main.ui uses forge_domain.agent, so a change to forge_domain.agent can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.agent.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
forge_main.ui uses forge_domain.conversation, so a change to forge_domain.conversation can break forge_main.ui, while a change to forge_main.ui can't break forge_domain.conversation.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
forge_main.ui uses forge_app.dto.anthropic.response, so a change to forge_app.dto.anthropic.response can break forge_main.ui, while a change to forge_main.ui can't break forge_app.dto.anthropic.response.
Position
Below the diagonal: forge_main.ui uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in forge_main.ui uses a type in forge_main.info.
The types involved
forge_main.ui.UI → forge_main.info.Info
Direction
forge_main.ui uses forge_main.info, so a change to forge_main.info can break forge_main.ui, while a change to forge_main.ui can't break forge_main.info.
Position
Below the diagonal: forge_main.ui 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
58
High / Critical
A03:2025 — Software Supply Chain Failures
41
High / Critical
Roadmap
Top priorities: Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
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 — 68
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 — 324
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 — 21
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 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 52 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 461 of 502 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.
D8 Code Coverage — 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. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`cargo llvm-cov`) shows coverage is measured in your own CI.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 254 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
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.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
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 — 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 source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
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.
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.
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.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
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.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
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.
38 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was UI::handle_subcommands at 83. A further 7 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 AppCommand::name at 46 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/forge_domain/src/provider.rs (ProviderId::from_str at 42), crates/forge_app/src/tool_executor.rs (ToolExecutor::call_internal at 17), crates/forge_domain/src/tools/catalog.rs (ToolCatalog::description 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.
+ 18 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with UI::handle_subcommands (cyclomatic 83). — Refactoring it lifts Cyclomatic Complexity from 6.2 to about 6.5/10.
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.
+ 35 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with forge_app::utils::sanitize_gemini_schema (cognitive 107), UI::handle_subcommands (cognitive 104), forge_markdown_stream::table::wrap (cognitive 99). — 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 5.7 to about 6.4/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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 Classes9.1 / 10Stronggated by 31 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 FileTooLong finding(s) in God Classes — start with ui.rs, preview.rs, strategy.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 10 MethodTooLong finding(s) in God Classes — start with ui.rs (3), operation.rs, response.rs. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 6 FunctionTooLong finding(s) in God Classes — start with preview.rs (2), utils.rs, conversation_html.rs. — One of this dimension's main actionable groups (6 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.
70 duplicated block group(s) detected. 2.1 % of the production lines (2,428 of 116,561) are in a reported copy. A further 35 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 55 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 8 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with response.rs, github_copilot_reasoning.rs, conversation_html.rs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with policy.rs, repository.rs, lib.rs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with anthropic.rs (3), response.rs, user_prompt.rs. — One of this dimension's main actionable groups (6 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.2 / 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.
25 production modules (Cargo+npm), 0 dependency cycle(s), 3 unstable depended-on module(s). Read from the build's own module declarations; 8 module(s) off the main sequence, with abstractness counted on 23 of the 25 (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: forge_display · ×8
Unstable project forge_api
Unstable project forge_infra
Unstable project forge_repo
What to do
Resolve the 8 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 1 Unstable project forge_api finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Unstable project forge_infra finding(s) in Coupling. — One of this dimension's main actionable groups (1 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.
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.
16 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: aws-config · ×16
✓ On the Gold path — maintain.
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.
1 of 845 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. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
Banned license: html2md
What to do
Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/forge_json_repair/src/schema_coercion.rs. Counted over 288 of the 462 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
✓ 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.
19 deducted task-comment markers across 116561 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 19 TodoComment finding(s) in Explicit Debt — start with agent_provider_resolver.rs (2), request.rs (2), walker.rs. — One of this dimension's main actionable groups (19 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. 9 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
Resolve the 3 redundant comment finding(s) in Comment Value — start with REDACTED (2), llm_judge.ts. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
2 of 25 build units (Cargo, npm) 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).
58 finding(s): 0 critical, 57 high, 1 medium, 0 low. 34 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `.forge/skills/write-release-notes/scripts/fetch-release-data.sh` (line 8), `scripts/benchmark.sh` (line 79), `scripts/list-all-porcelain.sh` (line 36), `scripts/test-zsh-utils.sh` (line 162, line 172, line 182, …), `shell-plugin/doctor.zsh` (line 196, lines 219–222, line 297, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
No action in Static Analysis (SAST) — all 34 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 (34 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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 warning-level).
Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-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.
50 of 288 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/forge_markdown_stream/src/table.rs. Counted over 288 of the 462 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with table.rs, oauth_callback.rs. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 48 Orphaned file finding(s) in Knowledge Freshness — start with result.rs (2), event_stream.rs, truncate_shell.rs. — One of this dimension's main actionable groups (48 recommendation-level).
Resolve the 1 Further orphaned files (smaller) 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.
Resolve the 11 Change coupling finding(s) in Change Coupling — start with services.rs (2), drop_tool_call.rs, tool_executor.rs. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 4 Change-coupling hub finding(s) in Change Coupling — start with orch.rs, fmt_input.rs, executor.rs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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 19 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 · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.agent-conversation a` sets color: #2563eb on background-color: #dbeafe — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:271, crates/forge_domain/src/conversation_style.css:256
`.back-to-main a` sets color: #2563eb on background-color: #dbeafe — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:314, crates/forge_domain/src/conversation_style.css:299
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
DM4 · Rich vs anemic domain model7.6 / 10Strong✓ Tool-verified
Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`Walker` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside. — crates/forge_app/src/walker.rs:8
What to do
Move the domain logic onto the entity (invariant-enforcing `&mut self` commands) instead of a foreign service.
Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (diesel/sea-orm/sqlx) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Event Sourcing — Whether the recovery-replay fold is deterministic — state derived purely from each event's own fields, no clock/random/IO on the replay path.
Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.
Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.
Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.
Maturity · Maturity — Whether the 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.
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.
What to do
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.
Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
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?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`warn!` at line 209 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/skill.rs:209
`error!` at line 470 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/provider/provider_repo.rs:470
`debug!` at line 532 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/provider/provider_repo.rs:532
`debug!` at line 536 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/provider/provider_repo.rs:536
`warn!` at line 98 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/database/pool.rs:98
`debug!` at line 784 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_repo/src/conversation/conversation_record.rs:784
`warn!` at line 81 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/http.rs:81
`warn!` at line 88 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/http.rs:88
`warn!` at line 118 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:118
`info!` at line 147 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:147
`debug!` at line 224 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:224
`warn!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:228
`info!` at line 237 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:237
`warn!` at line 240 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:240
`info!` at line 279 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:279
`info!` at line 325 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:325
`info!` at line 371 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:371
`warn!` at line 375 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:375
`warn!` at line 611 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_infra/src/mcp_client.rs:611
`error!` at line 202 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/app.rs:202
`error!` at line 79 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/compact.rs:79
`debug!` at line 78 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/data_gen.rs:78
`info!` at line 90 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/data_gen.rs:90
`debug!` at line 103 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — crates/forge_app/src/data_gen.rs:103
Statically assessed 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; ≈16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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 — 3 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 — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X9 Subsumed condition operand — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 67 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 image/media element found in the parsed markup — AC1 not applicable here.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no exported interface declares behaviour
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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 — ~2056 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — N/A — too few peers to establish a naming convention (8696 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"]`.
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
D8 Code Coverage — Coverage not measured — Rust suite
DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
M4 Documentation accuracy — Not applicable: the 9 current-state document(s) make no claim of a kind M4 checks. 71 claim(s) of kinds M4 does not check were not checked (path 10, command argument 6, environment variable 55); M4 checks only links and versions and artefact counts.
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
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
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
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.
S1 Web-Security Posture — No web surface: 449 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 builds on an HTTP-server crate (`tiny_http` (Cargo.toml)) but serves no HTTP of its own: its production source starts no server (no `HttpServer::new`, `axum::serve`, `Server::bind`, tonic `Server::builder()…serve`, `rocket::build()`, `warp::serve`, `serve_connection` or the like — its examples and tests are not production source), so it is a library whose server controls belong to the application that serves it — HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library. If this codebase starts serving HTTP, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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
X29 Per-element action decided by a fixed element — 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
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Orphaned knowledge crates/forge_markdown_stream/src/table.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Orphaned knowledge crates/forge_main/src/oauth_callback.rs:1— No living knowledge remains for this large file — its last meaningful change has decayed away, so if it breaks, no one currently understands it. It does carry its own tests, so the behaviour is pinned even though the understanding is gone: schedule a read-through, using those tests as the specification, before the next change lands here.
Banned license: html2md — `html2md` 0.2.15 is published on crates.io under `GPL-3.0+`, which this policy bans, and it is in the SHIPPED closure of this repository's REDACTED — so it is compiled by everything that builds this repository, not just by its test harness. The expression was read as SPDX, not as text: an `OR` is a choice and is only charged when every branch is banned, while an `AND` binds you to both operands and is charged when either is. Replace the crate, or record an accepted exception.
D30 · Dependency Vulnerabilities· High vulnerability · ×1
REDACTED
DM4 · Rich vs anemic domain model· Anemic domain model · ×1
Anemic domain model: Walker crates/forge_app/src/walker.rs:8— `Walker` is a data-only domain entity with `pub` mutable state and no invariant-enforcing behaviour of its own, while the repo holds the logic in a foreign service/manager/use-case — the anemic domain model. Move the behaviour onto the entity so it enforces its own invariants (or make it an immutable value object with private fields) rather than being driven from outside.
TodoComment crates/forge_walker/src/walker.rs:136— // TODO: Convert to async and return a stream — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_tracker/src/collect/posthog.rs:97— // TODO: move http request to a dispatch — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_services/src/policy.rs:69— // TODO: Can return a diff later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_services/src/tool_services/fs_patch.rs:494— // TODO: use forge_fs — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_repo/src/provider/bedrock_cache.rs:16— // TODO: Implement it on Context or Conversation instead of ConverseStreamInput — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_repo/src/conversation/conversation_record.rs:535— // TODO: Move this deserialization logic into Conversation repo — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_main/src/state.rs:6— //TODO: UIState and ForgePrompt seem like the same thing and can be merged — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_infra/src/forge_infra.rs:38— // TODO: Drop the "Service" suffix. Use names like ForgeFileReader, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_domain/src/context.rs:294— //TODO: Rename to TextMessage — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_domain/src/model.rs:33— // TODO: add provider information to the model — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_domain/src/tools/catalog.rs:1188— // TODO: This is an extremely slow operation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_app/src/agent_provider_resolver.rs:35— // TODO: Needs review, should we throw an err here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_app/src/agent_provider_resolver.rs:62— // TODO: Needs review, should we throw an err here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_app/src/compact.rs:46— // TODO: Consider using `eviction.max(retention)` — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_app/src/services.rs:429— // TODO: We should move Snapshot service to Services from infra — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_app/src/user_prompt.rs:595— // todo list — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_app/src/transformers/trim_context_summary.rs:40— /// Todo operation - each todo_write is unique and won't be deduplicated — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_app/src/dto/openai/request.rs:162— // TODO: should be an enum — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment crates/forge_app/src/dto/anthropic/request.rs:407— // TODO: verify this Thinking variants don't support cache control — 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.
Change coupling: drop_tool_call.rs ↔ set_cache.rs crates/forge_app/src/dto/openai/transformers/drop_tool_call.rs:1— `crates/forge_app/src/dto/openai/transformers/drop_tool_call.rs` and `crates/forge_app/src/dto/openai/transformers/set_cache.rs` change together 92% of the time (12 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 12 shared commits counted here, the most recent 3 are `8c0af00b` fix: add GitHub Copilot optimization headers for billing. (#2813); `3c27238e` refactor(commit): request commit messages with json schema structured…; `d529c960` refactor: streaming control via context (#2066) — run `git show` on any of them.
Change coupling: tool_executor.rs ↔ summary.rs crates/forge_app/src/tool_executor.rs:1— `crates/forge_app/src/tool_executor.rs` and `crates/forge_domain/src/compact/summary.rs` change together 77% of the time (10 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `9d5094fb` feat: subagent as task (#2508); `98732649` feat(tools): add multi_patch tool for batch file edits (#2840); `a7a77f7f` fix(semantic_search): remove extensions field (#2339) — run `git show` on any of them.
Change coupling: attachment.rs ↔ shell.rs crates/forge_services/src/attachment.rs:1— `crates/forge_services/src/attachment.rs` and `crates/forge_services/src/tool_services/shell.rs` change together 67% of the time (8 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `4dd37a8b` feat(permissions): enable permission checks only in restricted mode (…; `038552d7` feat: support Streaming HTTP (#1864); `4c4c35e4` refactor: use `faker` to generate env in tests (#1767) — run `git show` on any of them.
Change coupling: services.rs ↔ repo.rs crates/forge_app/src/services.rs:1— `crates/forge_app/src/services.rs` and `crates/forge_domain/src/repo.rs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `6481375e` refactor(workspace): rename codebase to workspace in types and servic…; `e86205fc` fix(operation): use cdata for warning messages to prevent html escapi…; `5a805e25` feat: add conversation delete command (#2077) — run `git show` on any of them.
Change coupling: services.rs ↔ lib.rs crates/forge_app/src/services.rs:1— `crates/forge_app/src/services.rs` and `crates/forge_services/src/lib.rs` change together 62% of the time (8 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `96509376` fix(sync): use env-based batch size for consistent file-read concurre…; `6e20da27` feat: ability to define provider per agent (#1705); `1a22db8b` feat: ability to define commands in MD (#1708) — run `git show` on any of them.
Change coupling: orch_setup.rs ↔ env.rs crates/forge_app/src/orch_spec/orch_setup.rs:1— `crates/forge_app/src/orch_spec/orch_setup.rs` and `crates/forge_infra/src/env.rs` change together 59% of the time (20 of the 34 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 20 shared commits counted here, the most recent 3 are `279ec190` feat(config): allow configuration of the base_path (#2864); `e75c7837` chore(provider): increase model cache TTL to one week (#2588); `e25c1c08` fix: add FIXME comments for EMFILE risk in unbounded parallel file re… — run `git show` on any of them.
Change coupling: forge_api.rs ↔ app_config.rs crates/forge_api/src/forge_api.rs:1— `crates/forge_api/src/forge_api.rs` and `crates/forge_services/src/app_config.rs` change together 59% of the time (10 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `a387bfd0` refactor(config): replace get_default_provider/get_provider_model wit…; `bfd9f7fc` fix: atomic provider and model selection with proper cancellation han…; `da37b431` Feat(suggest-model): add suggest model command (#2511) — run `git show` on any of them.
Change coupling: prompt.rs ↔ state.rs crates/forge_main/src/prompt.rs:1— `crates/forge_main/src/prompt.rs` and `crates/forge_main/src/state.rs` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `79cae5d7` feat: support for current working directory (#1174); `86901d15` refactor: update agent names to Forge and Fuse (#930); `577fb935` feat: allow user to select agents interactively (#919) — run `git show` on any of them.
Change coupling: banner.rs ↔ model.rs crates/forge_main/src/banner.rs:1— `crates/forge_main/src/banner.rs` and `crates/forge_main/src/model.rs` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency 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 7 shared commits counted here, the most recent 3 are `16f54bbc` feat(repl): bring REPL to feature parity with ZSH shell plugin (#2984); `c6dfcfb9` fix: correct command references from "/conversations" to "/conversati…; `75950bfb` feat: add `/usage` command (#1365) — run `git show` on any of them.
Change coupling: env.rs ↔ shell.rs crates/forge_infra/src/env.rs:1— `crates/forge_infra/src/env.rs` and `crates/forge_services/src/tool_services/shell.rs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `d96f8f91` fix: add fallback from rbash to bash/zsh/sh for command execution (#2…; `4dd37a8b` feat(permissions): enable permission checks only in restricted mode (…; `038552d7` feat: support Streaming HTTP (#1864) — run `git show` on any of them.
Change coupling: operation.rs ↔ fs_read.rs crates/forge_app/src/operation.rs:1— `crates/forge_app/src/operation.rs` and `crates/forge_services/src/tool_services/fs_read.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `29db91a4` fix(attachment): hash full file content instead of range content and …; `5ed3660d` feat(tools): enhance read tool description with detailed usage guidel…; `9298b626` fix: hash computation for externally modified files (#1979) — run `git show` on any of them.
UI::handle_subcommands (cognitive 104) crates/forge_main/src/ui.rs:466— UI::handle_subcommands has cognitive complexity 104 (threshold 15). Drivers by points: if/else 31 (73 pts), match/switch 9 (17 pts), loops 4 (13 pts), boolean chains 1 (nesting depth added 59). 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.
UI::select_model (cognitive 45) crates/forge_main/src/ui.rs:2904— UI::select_model has cognitive complexity 45 (threshold 15). Drivers by points: if/else 20 (35 pts), loops 5 (7 pts), boolean chains 2, match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UI::on_dump (cognitive 32) crates/forge_main/src/ui.rs:4067— UI::on_dump has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (32 pts) (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.
UI::on_show_models (cognitive 30) crates/forge_main/src/ui.rs:1426— UI::on_show_models has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (26 pts), loops 2 (3 pts), match/switch 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UI::run_inner (cognitive 29) crates/forge_main/src/ui.rs:358— UI::run_inner has cognitive complexity 29 (threshold 15). Drivers by points: match/switch 5 (14 pts), if/else 5 (13 pts), boolean chains 1, loops 1 (nesting depth added 17). 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.
UI::on_command (cognitive 27) crates/forge_main/src/ui.rs:2167— UI::on_command has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (26 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
UI::handle_api_key_input (cognitive 27) crates/forge_main/src/ui.rs:3085— UI::handle_api_key_input has cognitive complexity 27 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 2 (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.
UI::handle_chat_response (cognitive 25) crates/forge_main/src/ui.rs:4140— UI::handle_chat_response has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 3 (5 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UI::on_index (cognitive 21) crates/forge_main/src/ui.rs:4752— UI::on_index has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 1 (2 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.
UI::on_show_mcp_servers (cognitive 19) crates/forge_main/src/ui.rs:1730— UI::on_show_mcp_servers has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (6 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileTooLong: src/ui.rs crates/forge_main/src/ui.rs— FileTooLong — 3313 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 97% of them inside a single declaration: A (119-5211). The bar is 500 significant lines; this is 2813 over it, 6.63× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/preview.rs crates/forge_select/src/preview.rs— FileTooLong — 942 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 442 over it, 1.88× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: auth/strategy.rs crates/forge_infra/src/auth/strategy.rs— FileTooLong — 770 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 270 over it, 1.54× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/services.rs crates/forge_app/src/services.rs— FileTooLong — 681 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 181 over it, 1.36× 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/parser.rs crates/forge_json_repair/src/parser.rs— FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 99% of them inside a single declaration: JsonRepairParser (2 blocks, 5-1073). The bar is 500 significant lines; this is 181 over it, 1.36× 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: conversation/conversation_record.rs crates/forge_repo/src/conversation/conversation_record.rs— FileTooLong — 675 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 175 over it, 1.35× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: provider/bedrock.rs crates/forge_repo/src/provider/bedrock.rs— FileTooLong — 661 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 161 over it, 1.32× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: tools/catalog.rs crates/forge_domain/src/tools/catalog.rs— FileTooLong — 586 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 86 over it, 1.17× 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/context.rs crates/forge_domain/src/context.rs— FileTooLong — 505 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 5 over it, 1.01× 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/utils.rs crates/forge_app/src/utils.rs— FileTooLong — 502 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 2 over it, 1.00× 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.
MethodTooLong: ToolOperation.into_tool_output crates/forge_app/src/operation.rs:235— MethodTooLong — into_tool_output runs 343 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 243 over it, 3.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: UI.handle_subcommands crates/forge_main/src/ui.rs:466— MethodTooLong — handle_subcommands runs 295 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 195 over it, 2.95× 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: UI.on_command crates/forge_main/src/ui.rs:2167— MethodTooLong — on_command runs 177 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 77 over it, 1.77× 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: ChatCompletionMessage.try_from crates/forge_app/src/dto/openai/response.rs:324— MethodTooLong — try_from runs 168 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 68 over it, 1.68× 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: ToolExecutor.call_internal crates/forge_app/src/tool_executor.rs:151— MethodTooLong — call_internal runs 154 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 54 over it, 1.54× 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: JsonRepairParser.parse_string crates/forge_json_repair/src/parser.rs:348— MethodTooLong — parse_string runs 143 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 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Orchestrator.run crates/forge_app/src/orch.rs:245— MethodTooLong — run runs 133 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 33 over it, 1.33× 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: UI.select_model crates/forge_main/src/ui.rs:2904— MethodTooLong — select_model runs 114 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 14 over it, 1.14× 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: Renderer.render_event crates/forge_markdown_stream/src/renderer.rs:126— MethodTooLong — render_event runs 114 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 14 over it, 1.14× 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: ForgeApp.chat crates/forge_app/src/app.rs:60— MethodTooLong — chat runs 103 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 3 over it, 1.03× 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×10
Duplicated block (8 lines × 2) crates/forge_app/src/dto/openai/response.rs:349— crates/forge_app/src/dto/openai/response.rs:349-356 | crates/forge_app/src/dto/openai/response.rs:416-424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_app/src/dto/openai/response.rs:349` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) crates/forge_app/src/dto/openai/transformers/github_copilot_reasoning.rs:20— crates/forge_app/src/dto/openai/transformers/github_copilot_reasoning.rs:20-27 | crates/forge_app/src/dto/openai/transformers/reasoning_content.rs:21-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_app/src/dto/openai/transformers/github_copilot_reasoning.rs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/forge_domain/src/conversation_html.rs:29— crates/forge_domain/src/conversation_html.rs:29-36 | crates/forge_domain/src/conversation_html.rs:110-117 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_domain/src/conversation_html.rs:29` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) crates/forge_eventsource_stream/src/event_stream.rs:246— crates/forge_eventsource_stream/src/event_stream.rs:246-253 | crates/forge_eventsource_stream/src/event_stream.rs:274-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/forge_services/src/tool_services/fs_patch.rs:271— crates/forge_services/src/tool_services/fs_patch.rs:271-278 | crates/forge_services/src/tool_services/fs_patch.rs:294-301 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) crates/forge_domain/src/message.rs:43— crates/forge_domain/src/message.rs:43-50 | crates/forge_domain/src/message.rs:71-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_domain/src/message.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 (8 lines × 2) crates/forge_repo/src/provider/openai.rs:331— crates/forge_repo/src/provider/openai.rs:331-339 | crates/forge_repo/src/provider/openai_responses/repository.rs:712-719 — before extracting anything, compare `crates/forge_repo/src/provider/openai.rs` and `crates/forge_repo/src/provider/openai_responses/repository.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/openai.rs:331` 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) crates/forge_main/src/ui.rs:4580— crates/forge_main/src/ui.rs:4580-4587 | crates/forge_main/src/ui.rs:4590-4597 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:4580` 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.
Off the main sequence: forge_display — forge_display: 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: forge_json_repair — forge_json_repair: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: forge_select — forge_select: 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: forge_stream — forge_stream: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: forge_walker — forge_walker: 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: forge_config — forge_config: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: forge_fs — forge_fs: abstractness 0.00, instability 0.17, distance 0.83 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Off the main sequence: forge_eventsource_stream — forge_eventsource_stream: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Duplicated block (7 lines × 2) crates/forge_domain/src/policies/policy.rs:39— crates/forge_domain/src/policies/policy.rs:39-46 | crates/forge_domain/src/policies/policy.rs:48-54 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) crates/forge_repo/src/provider/openai_responses/repository.rs:264— crates/forge_repo/src/provider/openai_responses/repository.rs:264-270 | crates/forge_repo/src/provider/openai_responses/repository.rs:273-279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/openai_responses/repository.rs:273` 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 (7 lines × 2) crates/forge_spinner/src/lib.rs:151— crates/forge_spinner/src/lib.rs:151-157 | crates/forge_spinner/src/lib.rs:166-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) crates/forge_main/src/ui.rs:1397— crates/forge_main/src/ui.rs:1397-1403 | crates/forge_main/src/ui.rs:3557-3563 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/forge_main/src/ui.rs:3564` calls `provider_type`, `to_string` and `crates/forge_main/src/ui.rs:1404` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) crates/forge_domain/src/tool_order.rs:92— crates/forge_domain/src/tool_order.rs:92-98 | crates/forge_domain/src/tool_order.rs:106-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `tools` to `&mut [ToolDefinition]` in one and `&mut [&ToolDefinition]` 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 (7 lines × 2) crates/forge_infra/src/http.rs:273— crates/forge_infra/src/http.rs:273-279 | crates/forge_repo/src/provider/utils.rs:11-17 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/utils.rs:11` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) crates/forge_app/src/operation.rs:533— crates/forge_app/src/operation.rs:533-539 | crates/forge_app/src/operation.rs:541-547 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
FunctionTooLong: forge_select::preview::draw_preview_ui crates/forge_select/src/preview.rs:876— FunctionTooLong — forge_select::preview::draw_preview_ui runs 247 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 147 over it, 2.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.
FunctionTooLong: forge_select::preview::run_select_ui_values crates/forge_select/src/preview.rs:289— FunctionTooLong — forge_select::preview::run_select_ui_values runs 235 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 135 over it, 2.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: forge_app::utils::sanitize_gemini_schema crates/forge_app/src/utils.rs:626— FunctionTooLong — forge_app::utils::sanitize_gemini_schema runs 142 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 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: forge_domain::conversation_html::create_conversation_context_section crates/forge_domain/src/conversation_html.rs:288— FunctionTooLong — forge_domain::conversation_html::create_conversation_context_section runs 127 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: forge_services::tool_services::fs_patch::apply_replacement crates/forge_services/src/tool_services/fs_patch.rs:202— FunctionTooLong — forge_services::tool_services::fs_patch::apply_replacement runs 114 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 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: forge_markdown_stream::table::wrap crates/forge_markdown_stream/src/table.rs:135— FunctionTooLong — forge_markdown_stream::table::wrap runs 110 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities· Medium advisory (unmaintained) · ×6
Duplicated block (13 lines × 2) crates/forge_app/src/dto/openai/response.rs:384— crates/forge_app/src/dto/openai/response.rs:384-396 | crates/forge_app/src/dto/openai/response.rs:451-463 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_app/src/dto/openai/response.rs:384` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) crates/forge_app/src/user_prompt.rs:76— crates/forge_app/src/user_prompt.rs:76-88 | crates/forge_app/src/user_prompt.rs:122-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_app/src/user_prompt.rs:76` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/forge_repo/src/provider/anthropic.rs:267— crates/forge_repo/src/provider/anthropic.rs:267-279 | crates/forge_repo/src/provider/google.rs:101-113 — before extracting anything, compare `crates/forge_repo/src/provider/anthropic.rs` and `crates/forge_repo/src/provider/google.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/anthropic.rs:267` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/forge_repo/src/provider/anthropic.rs:284— crates/forge_repo/src/provider/anthropic.rs:284-296 | crates/forge_repo/src/provider/google.rs:124-136 — before extracting anything, compare `crates/forge_repo/src/provider/anthropic.rs` and `crates/forge_repo/src/provider/google.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/anthropic.rs:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) crates/forge_services/src/tool_services/fs_search.rs:330— crates/forge_services/src/tool_services/fs_search.rs:330-342 | crates/forge_services/src/tool_services/fs_search.rs:368-380 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `self` to `mut` in one and `&mut` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 2) crates/forge_repo/src/provider/anthropic.rs:302— crates/forge_repo/src/provider/anthropic.rs:302-314 | crates/forge_repo/src/provider/openai_responses/repository.rs:382-394 — before extracting anything, compare `crates/forge_repo/src/provider/anthropic.rs` and `crates/forge_repo/src/provider/openai_responses/repository.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
forge_markdown_stream::table::wrap (cognitive 99) crates/forge_markdown_stream/src/table.rs:135— forge_markdown_stream::table::wrap has cognitive complexity 99 (threshold 15). Drivers by points: if/else 27 (78 pts), loops 4 (15 pts), boolean chains 6 (nesting depth added 62). 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.
forge_markdown_stream::table::split_word_at_width (cognitive 59) crates/forge_markdown_stream/src/table.rs:304— forge_markdown_stream::table::split_word_at_width has cognitive complexity 59 (threshold 15). Drivers by points: if/else 14 (46 pts), loops 3 (11 pts), boolean chains 2 (nesting depth added 40). 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.
forge_markdown_stream::table::render_table (cognitive 25) crates/forge_markdown_stream/src/table.rs:10— forge_markdown_stream::table::render_table has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 5 (8 pts), boolean chains 3 (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.
forge_markdown_stream::utils::collapse_ansi_codes (cognitive 22) crates/forge_markdown_stream/src/utils.rs:340— forge_markdown_stream::utils::collapse_ansi_codes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_markdown_stream::utils::parse_atoms (cognitive 16) crates/forge_markdown_stream/src/utils.rs:261— forge_markdown_stream::utils::parse_atoms has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (5 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.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×5
Edited copy of a member (13 corresponding lines) crates/forge_domain/src/message.rs:38— crates/forge_domain/src/message.rs:38-50 | crates/forge_domain/src/message.rs:66-78 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/forge_main/src/ui.rs:2491— crates/forge_main/src/ui.rs:2491-2503 | crates/forge_main/src/ui.rs:2506-2518 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/forge_services/src/clipper.rs:116— crates/forge_services/src/clipper.rs:116-128 | crates/forge_services/src/clipper.rs:136-152 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/forge_repo/src/agent.rs:177— crates/forge_repo/src/agent.rs:177-189 | crates/forge_services/src/command.rs:135-147 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) crates/forge_config/src/compact.rs:106— crates/forge_config/src/compact.rs:106-118 | crates/forge_domain/src/compact/compact_config.rs:115-127 — 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.
Duplicated block (9 lines × 2) crates/forge_app/src/dto/openai/response.rs:360— crates/forge_app/src/dto/openai/response.rs:360-368 | crates/forge_app/src/dto/openai/response.rs:428-436 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_app/src/dto/openai/response.rs:360` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/forge_json_repair/src/schema_coercion.rs:77— crates/forge_json_repair/src/schema_coercion.rs:77-85 | crates/forge_json_repair/src/schema_coercion.rs:88-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_json_repair/src/schema_coercion.rs:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/forge_app/src/template_engine.rs:27— crates/forge_app/src/template_engine.rs:27-35 | crates/forge_app/src/template_engine.rs:43-54 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_app/src/template_engine.rs:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) crates/forge_repo/src/agent.rs:89— crates/forge_repo/src/agent.rs:89-97 | crates/forge_services/src/command.rs:77-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) crates/forge_app/src/operation.rs:250— crates/forge_app/src/operation.rs:250-258 | crates/forge_app/src/operation.rs:283-291 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_app/src/operation.rs:250` 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.
Low contrast colour pair in CSS (4.2:1) crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:271— `.agent-conversation a` sets color: #2563eb on background-color: #dbeafe — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.2:1) crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:314— `.back-to-main a` sets color: #2563eb on background-color: #dbeafe — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.2:1) crates/forge_domain/src/conversation_style.css:256— `.agent-conversation a` sets color: #2563eb on background-color: #dbeafe — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.2:1) crates/forge_domain/src/conversation_style.css:299— `.back-to-main a` sets color: #2563eb on background-color: #dbeafe — 4.2:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
UI::handle_subcommands (cyclomatic 83) crates/forge_main/src/ui.rs:466— UI::handle_subcommands has cyclomatic complexity 83 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: crates/forge_main/src/ui.rs holds 4 of the 38 functions over the threshold — including the worst — and 123 of the 436 points over it (28%), 2× the next-largest file (crates/forge_select/src/preview.rs at 61). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
UI::on_command (cyclomatic 56) crates/forge_main/src/ui.rs:2167— UI::on_command has cyclomatic complexity 56 (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. This file is where this pass's cyclomatic complexity CONCENTRATES: crates/forge_main/src/ui.rs holds 4 of the 38 functions over the threshold — including the worst — and 123 of the 436 points over it (28%), 2× the next-largest file (crates/forge_select/src/preview.rs at 61). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
UI::select_model (cyclomatic 24) crates/forge_main/src/ui.rs:2904— UI::select_model 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. This file is where this pass's cyclomatic complexity CONCENTRATES: crates/forge_main/src/ui.rs holds 4 of the 38 functions over the threshold — including the worst — and 123 of the 436 points over it (28%), 2× the next-largest file (crates/forge_select/src/preview.rs at 61). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
UI::handle_chat_response (cyclomatic 20) crates/forge_main/src/ui.rs:4140— UI::handle_chat_response has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: crates/forge_main/src/ui.rs holds 4 of the 38 functions over the threshold — including the worst — and 123 of the 436 points over it (28%), 2× the next-largest file (crates/forge_select/src/preview.rs at 61). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
JsonRepairParser::parse_string (cyclomatic 37) crates/forge_json_repair/src/parser.rs:348— JsonRepairParser::parse_string has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JsonRepairParser::parse_unquoted_string (cyclomatic 25) crates/forge_json_repair/src/parser.rs:694— JsonRepairParser::parse_unquoted_string has cyclomatic complexity 25 (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.
JsonRepairParser::parse_number (cyclomatic 18) crates/forge_json_repair/src/parser.rs:595— JsonRepairParser::parse_number 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.
JsonRepairParser::parse_object (cyclomatic 17) crates/forge_json_repair/src/parser.rs:195— JsonRepairParser::parse_object has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
forge_app::utils::sanitize_gemini_schema (cognitive 107) crates/forge_app/src/utils.rs:626— forge_app::utils::sanitize_gemini_schema has cognitive complexity 107 (threshold 15). Drivers by points: if/else 23 (64 pts), loops 8 (26 pts), boolean chains 10, match/switch 3 (7 pts) (nesting depth added 63). 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.
forge_app::utils::enforce_strict_schema (cognitive 28) crates/forge_app/src/utils.rs:448— forge_app::utils::enforce_strict_schema has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 4, loops 1 (2 pts), match/switch 1 (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
forge_app::fmt::todo_fmt::format_todos_diff (cognitive 20) crates/forge_app/src/fmt/todo_fmt.rs:56— forge_app::fmt::todo_fmt::format_todos_diff has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 1 (4 pts), loops 2, 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.
forge_app::dto::anthropic::response::get_context_length (cognitive 16) crates/forge_app/src/dto/anthropic/response.rs:81— forge_app::dto::anthropic::response::get_context_length has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 6. 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.
JsonRepairParser::parse_string (cognitive 83) crates/forge_json_repair/src/parser.rs:348— JsonRepairParser::parse_string has cognitive complexity 83 (threshold 15). Drivers by points: if/else 27 (61 pts), loops 3 (10 pts), boolean chains 8, match/switch 1 (4 pts) (nesting depth added 44). 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.
JsonRepairParser::parse_unquoted_string (cognitive 47) crates/forge_json_repair/src/parser.rs:694— JsonRepairParser::parse_unquoted_string has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (32 pts), loops 5 (9 pts), boolean chains 6 (nesting depth added 21). 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.
JsonRepairParser::parse_object (cognitive 33) crates/forge_json_repair/src/parser.rs:195— JsonRepairParser::parse_object has cognitive complexity 33 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 4, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsonRepairParser::parse_number (cognitive 28) crates/forge_json_repair/src/parser.rs:595— JsonRepairParser::parse_number has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_select::preview::run_select_ui_values (cognitive 78) crates/forge_select/src/preview.rs:289— forge_select::preview::run_select_ui_values has cognitive complexity 78 (threshold 15). Drivers by points: if/else 23 (58 pts), match/switch 4 (13 pts), boolean chains 5, loops 2 (nesting depth added 44). 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.
forge_select::preview::draw_preview_ui (cognitive 57) crates/forge_select/src/preview.rs:876— forge_select::preview::draw_preview_ui has cognitive complexity 57 (threshold 15). Drivers by points: if/else 19 (39 pts), loops 5 (8 pts), match/switch 4 (7 pts), boolean chains 3 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_select::preview::wrap_ansi_line (cognitive 27) crates/forge_select/src/preview.rs:1194— forge_select::preview::wrap_ansi_line has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (22 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_select::preview::handle_key_event (cognitive 18) crates/forge_select/src/preview.rs:623— forge_select::preview::handle_key_event has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 4 (8 pts), match/switch 1 (nesting depth added 4). 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.
forge_domain::conversation_html::create_conversation_context_section (cognitive 55) crates/forge_domain/src/conversation_html.rs:288— forge_domain::conversation_html::create_conversation_context_section has cognitive complexity 55 (threshold 15). Drivers by points: if/else 23 (49 pts), match/switch 2 (5 pts), boolean chains 1 (nesting depth added 29). 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.
forge_domain::conversation_html::create_info_table (cognitive 24) crates/forge_domain/src/conversation_html.rs:136— forge_domain::conversation_html::create_info_table has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (21 pts), match/switch 1 (3 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.
forge_domain::compact::summary::extract_tool_info (cognitive 21) crates/forge_domain/src/compact/summary.rs:339— forge_domain::compact::summary::extract_tool_info has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 2 (7 pts), loops 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_domain::compact::strategy::find_sequence_preserving_last_n (cognitive 16) crates/forge_domain/src/compact/strategy.rs:81— forge_domain::compact::strategy::find_sequence_preserving_last_n has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Change-coupling hub: orch.rs → agent_executor.rs, compact_config.rs, event.rs, system_context.rs, conversation.rs crates/forge_app/src/orch.rs— `crates/forge_app/src/orch.rs` changes together with 5 other files — `crates/forge_app/src/agent_executor.rs`, `crates/forge_domain/src/compact/compact_config.rs`, `crates/forge_domain/src/event.rs`, `crates/forge_domain/src/system_context.rs`, `crates/forge_services/src/conversation.rs` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: fmt_input.rs → operation.rs, tool_executor.rs, summary.rs crates/forge_app/src/fmt/fmt_input.rs— `crates/forge_app/src/fmt/fmt_input.rs` changes together with 3 other files — `crates/forge_app/src/operation.rs`, `crates/forge_app/src/tool_executor.rs`, `crates/forge_domain/src/compact/summary.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: executor.rs → operation.rs, attachment.rs, shell.rs crates/forge_infra/src/executor.rs— `crates/forge_infra/src/executor.rs` changes together with 3 other files — `crates/forge_app/src/operation.rs`, `crates/forge_services/src/attachment.rs`, `crates/forge_services/src/tool_services/shell.rs` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: api.rs → command_generator.rs, services.rs, repo.rs, app_config.rs, conversation.rs crates/forge_api/src/api.rs— `crates/forge_api/src/api.rs` changes together with 5 other files — `crates/forge_app/src/command_generator.rs`, `crates/forge_app/src/services.rs`, `crates/forge_domain/src/repo.rs`, `crates/forge_services/src/app_config.rs`, `crates/forge_services/src/conversation.rs` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Duplicated block (5 lines × 2) crates/forge_main/src/ui.rs:2495— crates/forge_main/src/ui.rs:2495-2499 | crates/forge_main/src/ui.rs:4516-4520 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:2495` 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 (5 lines × 2) crates/forge_markdown_stream/src/theme.rs:294— crates/forge_markdown_stream/src/theme.rs:294-298 | crates/forge_markdown_stream/src/theme.rs:341-345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) crates/forge_select/src/preview.rs:758— crates/forge_select/src/preview.rs:758-762 | crates/forge_select/src/preview.rs:785-789 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/forge_select/src/preview.rs:784` calls `max` and `crates/forge_select/src/preview.rs:757` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 2) crates/forge_select/src/preview.rs:791— crates/forge_select/src/preview.rs:791-795 | crates/forge_select/src/preview.rs:918-922 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_select/src/preview.rs:791` 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.
forge_app::utils::sanitize_gemini_schema (cyclomatic 45) crates/forge_app/src/utils.rs:626— forge_app::utils::sanitize_gemini_schema has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
forge_app::dto::anthropic::response::get_context_length (cyclomatic 17) crates/forge_app/src/dto/anthropic/response.rs:81— forge_app::dto::anthropic::response::get_context_length has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
forge_app::utils::enforce_strict_schema (cyclomatic 17) crates/forge_app/src/utils.rs:448— forge_app::utils::enforce_strict_schema has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
forge_select::preview::run_select_ui_values (cyclomatic 43) crates/forge_select/src/preview.rs:289— forge_select::preview::run_select_ui_values has cyclomatic complexity 43 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
forge_select::preview::handle_key_event (cyclomatic 35) crates/forge_select/src/preview.rs:623— forge_select::preview::handle_key_event has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
forge_select::preview::draw_preview_ui (cyclomatic 28) crates/forge_select/src/preview.rs:876— forge_select::preview::draw_preview_ui has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
forge_markdown_stream::table::wrap (cyclomatic 33) crates/forge_markdown_stream/src/table.rs:135— forge_markdown_stream::table::wrap has cyclomatic complexity 33 (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.
forge_markdown_stream::utils::collapse_ansi_codes (cyclomatic 29) crates/forge_markdown_stream/src/utils.rs:340— forge_markdown_stream::utils::collapse_ansi_codes has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
forge_markdown_stream::table::split_word_at_width (cyclomatic 17) crates/forge_markdown_stream/src/table.rs:304— forge_markdown_stream::table::split_word_at_width has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
forge_json_repair::schema_coercion::coerce_value_with_schema_object (cognitive 71) crates/forge_json_repair/src/schema_coercion.rs:38— forge_json_repair::schema_coercion::coerce_value_with_schema_object has cognitive complexity 71 (threshold 15). Drivers by points: if/else 24 (55 pts), loops 4 (9 pts), boolean chains 7 (nesting depth added 36). 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.
forge_json_repair::schema_coercion::coerce_array_value (cognitive 25) crates/forge_json_repair/src/schema_coercion.rs:323— forge_json_repair::schema_coercion::coerce_array_value has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 4 (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.
forge_json_repair::schema_coercion::try_coerce_string (cognitive 23) crates/forge_json_repair/src/schema_coercion.rs:243— forge_json_repair::schema_coercion::try_coerce_string has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D30 · Dependency Vulnerabilities· Medium advisory (unsound) · ×3
Duplicated block (12 lines × 2) crates/forge_json_repair/src/parser.rs:616— crates/forge_json_repair/src/parser.rs:616-627 | crates/forge_json_repair/src/parser.rs:634-645 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_json_repair/src/parser.rs:616` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/forge_json_repair/src/parser.rs:614` calls `current_char`, `Some` and `crates/forge_json_repair/src/parser.rs:633` 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 (12 lines × 2) crates/forge_main/src/ui.rs:516— crates/forge_main/src/ui.rs:516-527 | crates/forge_main/src/ui.rs:2107-2118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:516` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/forge_main/src/ui.rs:2103` calls `is_none` and `crates/forge_main/src/ui.rs:515` 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 (12 lines × 2) crates/forge_infra/src/auth/strategy.rs:185— crates/forge_infra/src/auth/strategy.rs:185-196 | crates/forge_infra/src/auth/strategy.rs:710-725 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_infra/src/auth/strategy.rs:185` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/forge_json_repair/src/parser.rs:598— crates/forge_json_repair/src/parser.rs:598-607 | crates/forge_json_repair/src/parser.rs:614-623 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_json_repair/src/parser.rs:598` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) crates/forge_select/src/multi.rs:33— crates/forge_select/src/multi.rs:33-42 | crates/forge_select/src/select.rs:87-96 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_select/src/multi.rs:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) crates/forge_repo/src/provider/openai_responses/response.rs:206— crates/forge_repo/src/provider/openai_responses/response.rs:206-215 | crates/forge_repo/src/provider/openai_responses/response.rs:234-243 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/openai_responses/response.rs:206` 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) crates/forge_infra/src/auth/strategy.rs:464— crates/forge_infra/src/auth/strategy.rs:464-469 | crates/forge_repo/src/provider/provider_repo.rs:516-524 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) crates/forge_main/src/ui.rs:1043— crates/forge_main/src/ui.rs:1043-1048 | crates/forge_main/src/ui.rs:1116-1121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:1043` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) crates/forge_app/src/utils.rs:103— crates/forge_app/src/utils.rs:103-108 | crates/forge_fs/src/lib.rs:30-35 — 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.
forge_json_repair::schema_coercion::coerce_value_with_schema_object (cyclomatic 36) crates/forge_json_repair/src/schema_coercion.rs:38— forge_json_repair::schema_coercion::coerce_value_with_schema_object has cyclomatic complexity 36 (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.
forge_json_repair::schema_coercion::try_coerce_string (cyclomatic 21) crates/forge_json_repair/src/schema_coercion.rs:243— forge_json_repair::schema_coercion::try_coerce_string has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChatCompletionMessage::try_from (cyclomatic 28) crates/forge_app/src/dto/openai/response.rs:324— ChatCompletionMessage::try_from has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ChatCompletionMessage::try_from (cyclomatic 17) crates/forge_app/src/dto/google/response.rs:451— ChatCompletionMessage::try_from has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
forge_domain::compact::summary::extract_tool_info (cyclomatic 22) crates/forge_domain/src/compact/summary.rs:339— forge_domain::compact::summary::extract_tool_info has cyclomatic complexity 22 (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.
forge_domain::conversation_html::create_conversation_context_section (cyclomatic 20) crates/forge_domain/src/conversation_html.rs:288— forge_domain::conversation_html::create_conversation_context_section 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.
ChatCompletionMessage::try_from (cognitive 76) crates/forge_app/src/dto/openai/response.rs:324— ChatCompletionMessage::try_from has cognitive complexity 76 (threshold 15). Drivers by points: if/else 18 (55 pts), loops 2 (10 pts), match/switch 4 (10 pts), boolean chains 1 (nesting depth added 51). 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.
ChatCompletionMessage::try_from (cognitive 35) crates/forge_app/src/dto/google/response.rs:451— ChatCompletionMessage::try_from has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (32 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_main::zsh::paste::wrap_tokens (cognitive 20) crates/forge_main/src/zsh/paste.rs:141— forge_main::zsh::paste::wrap_tokens has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_main::highlighter::highlight_mentions (cognitive 17) crates/forge_main/src/highlighter.rs:74— forge_main::highlighter::highlight_mentions has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (12 pts), if/else 1 (3 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
TooManyMethods: UI crates/forge_main/src/ui.rs:105— TooManyMethods — 116 methods. The bar is 30 methods; this is 86 over it, 3.87× 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: JsonRepairParser crates/forge_json_repair/src/parser.rs:5— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: JsonRepairParser crates/forge_json_repair/src/parser.rs:5— ClassTooLong — 676 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 48 methods, 2 blocks, lines 5-1073. The bar is 400 significant lines; this is 276 over it, 1.69× 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: ForgeRepo crates/forge_repo/src/forge_repo.rs:41— ClassTooLong — 416 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 28 blocks, lines 41-680. The bar is 400 significant lines; this is 16 over it, 1.04× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (45 corresponding lines) · ×2
Edited copy of a member (45 corresponding lines) crates/forge_markdown_stream/src/theme.rs:283— crates/forge_markdown_stream/src/theme.rs:283-327 | crates/forge_markdown_stream/src/theme.rs:330-374 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (45 corresponding lines) crates/forge_infra/src/auth/strategy.rs:223— crates/forge_infra/src/auth/strategy.rs:223-269 | crates/forge_infra/src/auth/strategy.rs:327-371 — These two members are one piece of code written twice and then edited apart: 45 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×2
Edited copy of a member (26 corresponding lines) crates/forge_json_repair/src/parser.rs:1008— crates/forge_json_repair/src/parser.rs:1008-1034 | crates/forge_json_repair/src/parser.rs:1036-1061 — 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.
Edited copy of a member (26 corresponding lines) crates/forge_infra/src/auth/strategy.rs:457— crates/forge_infra/src/auth/strategy.rs:457-499 | crates/forge_infra/src/auth/strategy.rs:501-526 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×2
Edited copy of a member (17 corresponding lines) crates/forge_services/src/auth.rs:20— crates/forge_services/src/auth.rs:20-38 | crates/forge_services/src/auth.rs:40-56 — 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.
Edited copy of a member (17 corresponding lines) crates/forge_app/src/utils.rs:17— crates/forge_app/src/utils.rs:17-33 | crates/forge_domain/src/tools/catalog.rs:1134-1150 — 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 copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) crates/forge_json_repair/src/parser.rs:147— crates/forge_json_repair/src/parser.rs:147-159 | crates/forge_json_repair/src/parser.rs:681-692 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) crates/forge_repo/src/agent.rs:138— crates/forge_repo/src/agent.rs:138-149 | crates/forge_services/src/command.rs:121-132 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) crates/forge_repo/src/agent.rs:54— crates/forge_repo/src/agent.rs:54-71 | crates/forge_services/src/command.rs:56-74 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) crates/forge_app/src/orch.rs:182— crates/forge_app/src/orch.rs:182-199 | crates/forge_app/src/system_prompt.rs:146-170 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×2
Edited copy of a member (10 corresponding lines) crates/forge_spinner/src/lib.rs:150— crates/forge_spinner/src/lib.rs:150-161 | crates/forge_spinner/src/lib.rs:165-174 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) crates/forge_markdown_stream/src/utils.rs:28— crates/forge_markdown_stream/src/utils.rs:28-39 | crates/forge_display/src/code.rs:40-49 — 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 copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) crates/forge_app/src/tool_executor.rs:133— crates/forge_app/src/tool_executor.rs:133-149 | crates/forge_infra/src/fs_write.rs:46-59 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) crates/forge_app/src/git_app.rs:80— crates/forge_app/src/git_app.rs:80-93 | crates/forge_services/src/tool_services/fs_read.rs:15-30 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (15 lines × 2) crates/forge_app/src/utils.rs:19— crates/forge_app/src/utils.rs:19-33 | crates/forge_domain/src/tools/catalog.rs:1136-1150 — 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 (15 lines × 2) crates/forge_json_repair/src/parser.rs:196— crates/forge_json_repair/src/parser.rs:196-210 | crates/forge_json_repair/src/parser.rs:274-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_json_repair/src/parser.rs:196` 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) crates/forge_domain/src/conversation_html.rs:181— crates/forge_domain/src/conversation_html.rs:181-191 | crates/forge_domain/src/conversation_html.rs:250-260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) crates/forge_main/src/ui.rs:4091— crates/forge_main/src/ui.rs:4091-4101 | crates/forge_main/src/ui.rs:4115-4125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:4091` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10–11 lines × 2) crates/forge_main/src/conversation_selector.rs:72— crates/forge_main/src/conversation_selector.rs:72-81 | crates/forge_main/src/ui.rs:2996-3006 — before extracting anything, compare `crates/forge_main/src/conversation_selector.rs` and `crates/forge_main/src/ui.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–11 lines × 2) crates/forge_main/src/ui.rs:1460— crates/forge_main/src/ui.rs:1460-1470 | crates/forge_main/src/ui.rs:2959-2968 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:1460` 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.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark crates/forge_domain/src/snapshots/forge_domain__conversation_html__tests__conversation.snap.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
ToolOperation::into_tool_output (cyclomatic 51) crates/forge_app/src/operation.rs:235— ToolOperation::into_tool_output has cyclomatic complexity 51 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
Renderer::render_event (cyclomatic 36) crates/forge_markdown_stream/src/renderer.rs:126— Renderer::render_event has cyclomatic complexity 36 (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.
ToolCatalog::to_content (cyclomatic 26) crates/forge_app/src/fmt/fmt_input.rs:9— ToolCatalog::to_content has cyclomatic complexity 26 (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.
forge_fs::binary_detection::is_binary_internal (cyclomatic 19) crates/forge_fs/src/binary_detection.rs:43— forge_fs::binary_detection::is_binary_internal has cyclomatic complexity 19 (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.
Walker::get_blocking (cyclomatic 19) crates/forge_walker/src/walker.rs:118— Walker::get_blocking has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Agent::apply_config (cyclomatic 18) crates/forge_app/src/agent.rs:95— Agent::apply_config 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.
ContextSummary::from (cyclomatic 17) crates/forge_domain/src/compact/summary.rs:218— ContextSummary::from has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolCallFull::try_from_parts (cyclomatic 17) crates/forge_domain/src/tools/call/tool_call.rs:106— ToolCallFull::try_from_parts has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ForgeCommandManager::parse (cyclomatic 17) crates/forge_main/src/model.rs:288— ForgeCommandManager::parse has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: AppCommand::name (cyclomatic 46) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded function is counted neither in this dimension's figures nor in its score.
OpenAIResponsesProvider::get_headers_for_conversation (cyclomatic 17) crates/forge_repo/src/provider/openai_responses/repository.rs:76— OpenAIResponsesProvider::get_headers_for_conversation has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
forge_services::tool_services::fs_patch::apply_replacement (cyclomatic 17) crates/forge_services/src/tool_services/fs_patch.rs:202— forge_services::tool_services::fs_patch::apply_replacement has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Response::into_domain (cyclomatic 16) crates/forge_repo/src/provider/openai_responses/response.rs:156— Response::into_domain 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.
DiffFormat::format (cyclomatic 16) crates/forge_display/src/diff.rs:50— DiffFormat::format 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.
OpenAIProvider::get_headers (cyclomatic 16) crates/forge_repo/src/provider/openai.rs:72— OpenAIProvider::get_headers has cyclomatic complexity 16 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ForgeProviderRepository::migrate_env_to_file (cyclomatic 16) crates/forge_repo/src/provider/provider_repo.rs:337— ForgeProviderRepository::migrate_env_to_file 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.
ToolOperation::into_tool_output (cognitive 82) crates/forge_app/src/operation.rs:235— ToolOperation::into_tool_output has cognitive complexity 82 (threshold 15). Drivers by points: if/else 19 (39 pts), loops 9 (26 pts), match/switch 7 (15 pts), boolean chains 2 (nesting depth added 45). 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.
ContextSummary::from (cognitive 46) crates/forge_domain/src/compact/summary.rs:218— ContextSummary::from has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (32 pts), loops 3 (11 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Response::into_domain (cognitive 43) crates/forge_repo/src/provider/openai_responses/response.rs:156— Response::into_domain has cognitive complexity 43 (threshold 15). Drivers by points: if/else 11 (27 pts), match/switch 3 (11 pts), loops 2 (5 pts) (nesting depth added 27). 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.
DiffFormat::format (cognitive 37) crates/forge_display/src/diff.rs:50— DiffFormat::format has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 7 (16 pts), match/switch 1 (4 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForgeProviderAuthService::refresh_provider_credential (cognitive 34) crates/forge_services/src/provider_auth.rs:149— ForgeProviderAuthService::refresh_provider_credential has cognitive complexity 34 (threshold 15). Drivers by points: if/else 6 (21 pts), match/switch 2 (10 pts), loops 1 (3 pts) (nesting depth added 25). 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.
ToolCallFull::try_from_parts (cognitive 33) crates/forge_domain/src/tools/call/tool_call.rs:106— ToolCallFull::try_from_parts has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (28 pts), boolean chains 4, loops 1 (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.
Orchestrator::run (cognitive 28) crates/forge_app/src/orch.rs:245— Orchestrator::run has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_infra::auth::strategy::poll_for_tokens (cognitive 28) crates/forge_infra/src/auth/strategy.rs:794— forge_infra::auth::strategy::poll_for_tokens has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZshRPrompt::fmt (cognitive 26) crates/forge_main/src/zsh/rprompt.rs:98— ZshRPrompt::fmt has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
forge_services::tool_services::fs_patch::apply_replacement (cognitive 25) crates/forge_services/src/tool_services/fs_patch.rs:202— forge_services::tool_services::fs_patch::apply_replacement has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 2 (4 pts), boolean chains 3, loops 1 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Message::from_domain (cognitive 24) crates/forge_repo/src/provider/bedrock.rs:762— Message::from_domain has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (6 pts), match/switch 2 (3 pts), boolean chains 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ForgeCommandManager::parse (cognitive 24) crates/forge_main/src/model.rs:288— ForgeCommandManager::parse has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 5, match/switch 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DoomLoopDetector::count_recent_pattern_repetitions (cognitive 22) crates/forge_app/src/hooks/doom_loop.rs:117— DoomLoopDetector::count_recent_pattern_repetitions has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_fs::binary_detection::is_binary_internal (cognitive 22) crates/forge_fs/src/binary_detection.rs:43— forge_fs::binary_detection::is_binary_internal has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 11, if/else 6 (9 pts), loops 1 (2 pts) (nesting depth added 4). 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.
ForgeMcpClient::create_connection (cognitive 21) crates/forge_infra/src/mcp_client.rs:95— ForgeMcpClient::create_connection has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (5 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 10). 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.
ForgeSkillRepository::load_skills_from_dir (cognitive 21) crates/forge_repo/src/skill.rs:119— ForgeSkillRepository::load_skills_from_dir has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 1 (2 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.
ForgeFetch::check_robots_txt (cognitive 21) crates/forge_services/src/tool_services/fetch.rs:31— ForgeFetch::check_robots_txt has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Walker::get_blocking (cognitive 21) crates/forge_walker/src/walker.rs:118— Walker::get_blocking has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (16 pts), match/switch 3, boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SanitizeToolIds::transform (cognitive 20) crates/forge_repo/src/provider/bedrock_sanitize_ids.rs:29— SanitizeToolIds::transform has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 2 (5 pts), match/switch 1 (4 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
forge_tool_macros::derive_description (cognitive 19) crates/forge_tool_macros/src/lib.rs:16— forge_tool_macros::derive_description has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Request::from (cognitive 18) crates/forge_app/src/dto/google/request.rs:302— Request::from has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), match/switch 3 (4 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TrimToolCallIds::transform (cognitive 18) crates/forge_app/src/dto/openai/transformers/trim_tool_call_ids.rs:12— TrimToolCallIds::transform has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForgeProviderRepository::migrate_env_to_file (cognitive 18) crates/forge_repo/src/provider/provider_repo.rs:337— ForgeProviderRepository::migrate_env_to_file has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AgentExecutor::execute (cognitive 17) crates/forge_app/src/agent_executor.rs:42— AgentExecutor::execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 2 (5 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContextMessage::to_text (cognitive 17) crates/forge_domain/src/context.rs:113— ContextMessage::to_text has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), match/switch 1 (nesting depth added 10). 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.
ForgeDirectoryReaderService::read_directory_files (cognitive 17) crates/forge_infra/src/fs_read_dir.rs:68— ForgeDirectoryReaderService::read_directory_files has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1, match/switch 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.
ForgePrompt::render_prompt_right (cognitive 17) crates/forge_main/src/prompt.rs:116— ForgePrompt::render_prompt_right has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, match/switch 1 (2 pts) (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.
ForgeFsSearch::search_content (cognitive 17) crates/forge_services/src/tool_services/fs_search.rs:421— ForgeFsSearch::search_content has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ForgeHttpInfra::new (cognitive 16) crates/forge_infra/src/http.rs:39— ForgeHttpInfra::new has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· from (cognitive 16) · ×1
Info::from (cognitive 16) crates/forge_main/src/info.rs:418— Info::from has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Renderer::render_event (cognitive 16) crates/forge_markdown_stream/src/renderer.rs:126— Renderer::render_event has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 4 (6 pts), match/switch 1 (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
TooManyFields: ForgeConfig crates/forge_config/src/config.rs:121— TooManyFields — 50 stored fields beside 2 methods. The bar is 30 stored fields; this is 20 over it, 1.67× 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.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) crates/forge_repo/src/provider/anthropic.rs:368— crates/forge_repo/src/provider/anthropic.rs:368-380 | crates/forge_repo/src/provider/bedrock.rs:1074-1087 | crates/forge_repo/src/provider/google.rs:200-212 | crates/forge_repo/src/provider/openai_responses/repository.rs:687-699 — 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 (57 corresponding lines) · ×1
Edited copy of a member (57 corresponding lines) crates/forge_repo/src/provider/openai.rs:72— crates/forge_repo/src/provider/openai.rs:72-128 | crates/forge_repo/src/provider/openai_responses/repository.rs:76-151 — These two members are one piece of code written twice and then edited apart: 57 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) crates/forge_repo/src/provider/anthropic.rs:253— crates/forge_repo/src/provider/anthropic.rs:253-296 | crates/forge_repo/src/provider/google.rs:93-136 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (56 corresponding lines) · ×1
Edited copy of a member (56 corresponding lines) crates/forge_services/src/tool_services/fs_patch.rs:482— crates/forge_services/src/tool_services/fs_patch.rs:482-537 | crates/forge_services/src/tool_services/fs_patch.rs:543-599 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×1
Edited copy of a member (31 corresponding lines) crates/forge_services/src/tool_services/fs_search.rs:213— crates/forge_services/src/tool_services/fs_search.rs:213-245 | crates/forge_services/src/tool_services/fs_search.rs:252-282 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) crates/forge_app/src/user_prompt.rs:62— crates/forge_app/src/user_prompt.rs:62-88 | crates/forge_app/src/user_prompt.rs:115-134 — 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) crates/forge_app/src/agent_provider_resolver.rs:26— crates/forge_app/src/agent_provider_resolver.rs:26-53 | crates/forge_app/src/agent_provider_resolver.rs:57-77 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 13+ corresponding lines) · ×1
Edited copies of one member (4 members, 13+ corresponding lines) crates/forge_repo/src/context_engine.rs:135— crates/forge_repo/src/context_engine.rs:135-150 | crates/forge_repo/src/context_engine.rs:302-314 | crates/forge_repo/src/context_engine.rs:321-340 | crates/forge_repo/src/context_engine.rs:372-384 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) crates/forge_domain/src/tool_order.rs:91— crates/forge_domain/src/tool_order.rs:91-98 | crates/forge_domain/src/tool_order.rs:105-112 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) crates/forge_main/src/porcelain.rs:58— crates/forge_main/src/porcelain.rs:58-70 | crates/forge_main/src/porcelain.rs:76-88 | crates/forge_main/src/porcelain.rs:187-207 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) crates/forge_infra/src/http.rs:135— crates/forge_infra/src/http.rs:135-145 | crates/forge_infra/src/http.rs:256-268 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) crates/forge_repo/src/provider/anthropic.rs:382— crates/forge_repo/src/provider/anthropic.rs:382-391 | crates/forge_repo/src/provider/google.rs:214-223 | crates/forge_repo/src/provider/openai.rs:421-429 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) crates/forge_domain/src/max_tokens.rs:84— crates/forge_domain/src/max_tokens.rs:84-94 | crates/forge_domain/src/temperature.rs:95-105 | crates/forge_domain/src/top_k.rs:82-92 | crates/forge_domain/src/top_p.rs:86-96 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) crates/forge_app/src/dto/anthropic/request.rs:326— crates/forge_app/src/dto/anthropic/request.rs:326-336 | crates/forge_app/src/dto/google/request.rs:548-556 — 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 (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) crates/forge_domain/src/temperature.rs:82— crates/forge_domain/src/temperature.rs:82-88 | crates/forge_domain/src/top_p.rs:73-79 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) crates/forge_app/src/orch.rs:174— crates/forge_app/src/orch.rs:174-179 | crates/forge_domain/src/tools/call/context.rs:21-26 — 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.
Duplicated block (54 lines × 2) crates/forge_json_repair/src/schema_coercion.rs:125— crates/forge_json_repair/src/schema_coercion.rs:125-178 | crates/forge_json_repair/src/schema_coercion.rs:328-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_json_repair/src/schema_coercion.rs:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (38 lines × 2) crates/forge_repo/src/provider/openai.rs:83— crates/forge_repo/src/provider/openai.rs:83-120 | crates/forge_repo/src/provider/openai_responses/repository.rs:87-124 — before extracting anything, compare `crates/forge_repo/src/provider/openai.rs` and `crates/forge_repo/src/provider/openai_responses/repository.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/openai.rs:83` 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 (26–27 lines × 2) crates/forge_markdown_stream/src/table.rs:149— crates/forge_markdown_stream/src/table.rs:149-175 | crates/forge_markdown_stream/src/table.rs:311-336 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_markdown_stream/src/table.rs:149` 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 (24 lines × 2) crates/forge_services/src/tool_services/fs_patch.rs:514— crates/forge_services/src/tool_services/fs_patch.rs:514-537 | crates/forge_services/src/tool_services/fs_patch.rs:576-599 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_services/src/tool_services/fs_patch.rs:514` 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) crates/forge_repo/src/provider/bedrock.rs:722— crates/forge_repo/src/provider/bedrock.rs:722-744 | crates/forge_repo/src/provider/bedrock.rs:856-878 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/bedrock.rs:722` 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) crates/forge_app/src/operation.rs:463— crates/forge_app/src/operation.rs:463-484 | crates/forge_app/src/operation.rs:486-507 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (19–20 lines × 2) crates/forge_infra/src/mcp_client.rs:407— crates/forge_infra/src/mcp_client.rs:407-425 | crates/forge_infra/src/mcp_client.rs:639-658 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_infra/src/mcp_client.rs:407` 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 (17–18 lines × 2) crates/forge_infra/src/auth/strategy.rs:243— crates/forge_infra/src/auth/strategy.rs:243-260 | crates/forge_infra/src/auth/strategy.rs:346-362 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_infra/src/auth/strategy.rs:243` 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 (16–18 lines × 2) crates/forge_main/src/conversation_selector.rs:58— crates/forge_main/src/conversation_selector.rs:58-75 | crates/forge_main/src/ui.rs:530-545 — before extracting anything, compare `crates/forge_main/src/conversation_selector.rs` and `crates/forge_main/src/ui.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/conversation_selector.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 (13–18 lines × 2) crates/forge_main/src/ui.rs:2066— crates/forge_main/src/ui.rs:2066-2083 | crates/forge_main/src/ui.rs:2196-2208 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:2066` 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–17 lines × 2) crates/forge_main/src/ui.rs:3163— crates/forge_main/src/ui.rs:3163-3179 | crates/forge_main/src/ui.rs:3186-3199 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:3163` 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 (17 lines × 2) crates/forge_repo/src/provider/openai_responses/repository.rs:245— crates/forge_repo/src/provider/openai_responses/repository.rs:245-261 | crates/forge_repo/src/provider/openai_responses/repository.rs:345-361 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/openai_responses/repository.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 (14–16 lines × 2) crates/forge_main/src/conversation_selector.rs:54— crates/forge_main/src/conversation_selector.rs:54-67 | crates/forge_main/src/ui.rs:2116-2131 — before extracting anything, compare `crates/forge_main/src/conversation_selector.rs` and `crates/forge_main/src/ui.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/conversation_selector.rs:54` 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–16 lines × 2) crates/forge_services/src/provider_auth.rs:37— crates/forge_services/src/provider_auth.rs:37-52 | crates/forge_services/src/provider_auth.rs:124-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_services/src/provider_auth.rs:37` 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 (7–14 lines × 3) crates/forge_main/src/ui.rs:2074— crates/forge_main/src/ui.rs:2074-2087 | crates/forge_main/src/ui.rs:2174-2180 | crates/forge_main/src/ui.rs:2203-2210 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:2074` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/forge_main/src/ui.rs:2180` calls `on_info`, `Some`, `list_conversations` and `crates/forge_main/src/ui.rs:2210` 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 (13–14 lines × 3) crates/forge_repo/src/provider/anthropic.rs:46— crates/forge_repo/src/provider/anthropic.rs:46-58 | crates/forge_repo/src/provider/openai.rs:75-88 | crates/forge_repo/src/provider/openai_responses/repository.rs:79-92 — before extracting anything, compare `crates/forge_repo/src/provider/anthropic.rs` and `crates/forge_repo/src/provider/openai_responses/repository.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/anthropic.rs:46` 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 (14 lines × 2) crates/forge_services/src/auth.rs:25— crates/forge_services/src/auth.rs:25-38 | crates/forge_services/src/auth.rs:43-56 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_services/src/auth.rs:25` 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 × 3) crates/forge_main/src/conversation_selector.rs:58— crates/forge_main/src/conversation_selector.rs:58-68 | crates/forge_main/src/ui.rs:529-540 | crates/forge_main/src/ui.rs:2120-2132 — before extracting anything, compare `crates/forge_main/src/conversation_selector.rs` and `crates/forge_main/src/ui.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/conversation_selector.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 (6–10 lines × 3) crates/forge_app/src/dto/anthropic/response.rs:362— crates/forge_app/src/dto/anthropic/response.rs:362-367 | crates/forge_app/src/dto/anthropic/response.rs:375-384 | crates/forge_app/src/dto/anthropic/response.rs:386-395 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_app/src/dto/anthropic/response.rs:362` 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 × 4) crates/forge_repo/src/provider/anthropic.rs:372— crates/forge_repo/src/provider/anthropic.rs:372-380 | crates/forge_repo/src/provider/bedrock.rs:1079-1087 | crates/forge_repo/src/provider/google.rs:204-212 | crates/forge_repo/src/provider/openai_responses/repository.rs:691-699 — before extracting anything, compare `crates/forge_repo/src/provider/anthropic.rs` and `crates/forge_repo/src/provider/google.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/anthropic.rs:372` 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 (7–9 lines × 2) crates/forge_repo/src/provider/openai_responses/repository.rs:229— crates/forge_repo/src/provider/openai_responses/repository.rs:229-237 | crates/forge_repo/src/provider/openai_responses/repository.rs:331-337 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_repo/src/provider/openai_responses/repository.rs:229` 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–9 lines × 2) crates/forge_services/src/tool_services/fs_patch.rs:320— crates/forge_services/src/tool_services/fs_patch.rs:320-327 | crates/forge_services/src/tool_services/fs_patch.rs:340-348 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_services/src/tool_services/fs_patch.rs:320` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/forge_services/src/tool_services/fs_patch.rs:318` calls `get`, `end`, `ok_or_else` and `crates/forge_services/src/tool_services/fs_patch.rs:339` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) crates/forge_app/src/operation.rs:302— crates/forge_app/src/operation.rs:302-308 | crates/forge_app/src/operation.rs:475-481 | crates/forge_app/src/operation.rs:498-504 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6–7 lines × 2) crates/forge_main/src/ui.rs:1450— crates/forge_main/src/ui.rs:1450-1456 | crates/forge_main/src/ui.rs:2951-2956 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_main/src/ui.rs:1450` 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 (5 lines × 3) crates/forge_services/src/tool_services/fs_patch.rs:249— crates/forge_services/src/tool_services/fs_patch.rs:249-254 | crates/forge_services/src/tool_services/fs_patch.rs:321-325 | crates/forge_services/src/tool_services/fs_patch.rs:341-345 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/forge_services/src/tool_services/fs_patch.rs:249` 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.
Low cohesion: Context (LCOM4 4) crates/forge_domain/src/context.rs:401— Context'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 crates/forge_eventsource_stream/src/event_stream.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 crates/forge_app/src/truncation/truncate_shell.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 crates/forge_domain/src/tool_order.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 crates/forge_markdown_stream/src/theme.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 crates/forge_app/src/terminal_context.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 crates/forge_markdown_stream/src/renderer.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 crates/forge_domain/src/policies/policy.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 crates/forge_eventsource/src/event_source.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 crates/forge_domain/src/message_pattern.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 crates/forge_template/src/element.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 crates/forge_markdown_stream/src/lib.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 crates/forge_app/src/hooks/tracing.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 crates/forge_app/src/transformers/dedupe_role.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 crates/forge_app/src/transformers/drop_role.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 crates/forge_app/src/dto/openai/transformers/set_reasoning_effort.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 crates/forge_domain/src/temperature.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 crates/forge_domain/src/top_p.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 crates/forge_domain/src/xml.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 crates/forge_domain/src/max_tokens.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 crates/forge_app/src/dto/openai/error.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 crates/forge_domain/src/top_k.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 crates/forge_app/src/truncation/truncate_search.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 crates/forge_fs/src/binary_detection.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 crates/forge_eventsource_stream/src/utf8_stream.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 crates/forge_domain/src/tools/result.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.
Interpolated log message defeats structured logging crates/forge_repo/src/skill.rs:209— `warn!` at line 209 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_repo/src/provider/provider_repo.rs:470— `error!` at line 470 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_repo/src/provider/provider_repo.rs:532— `debug!` at line 532 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_repo/src/provider/provider_repo.rs:536— `debug!` at line 536 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_repo/src/database/pool.rs:98— `warn!` at line 98 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_repo/src/conversation/conversation_record.rs:784— `debug!` at line 784 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/http.rs:81— `warn!` at line 81 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/http.rs:88— `warn!` at line 88 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:118— `warn!` at line 118 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:147— `info!` at line 147 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:224— `debug!` at line 224 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:228— `warn!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:237— `info!` at line 237 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:240— `warn!` at line 240 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:279— `info!` at line 279 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:325— `info!` at line 325 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:371— `info!` at line 371 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:375— `warn!` at line 375 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_infra/src/mcp_client.rs:611— `warn!` at line 611 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `warn!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_app/src/app.rs:202— `error!` at line 202 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_app/src/compact.rs:79— `error!` at line 79 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_app/src/data_gen.rs:78— `debug!` at line 78 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_app/src/data_gen.rs:90— `info!` at line 90 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `info!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
Interpolated log message defeats structured logging crates/forge_app/src/data_gen.rs:103— `debug!` at line 103 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`.
redundant comment benchmarks/evals/semantic_search_quality/llm_judge.ts:374— "Extract semantic search calls" repeats the code it sits on: 4 of its 4 words (extract, semantic, search, calls) are already in `const searches = extractSemanticSearchCalls(contextData);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:9— "Register Handlebars helper for escaping regex" repeats the code it sits on: 4 of its 5 words (register, handlebars, helper, regex) are already in `Handlebars.registerHelper("escapeRegex", escapeRegex);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:104— "Command failed with error" repeats the code it sits on: 3 of its 3 words (command, failed, error) are already in `return {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Silent fallback default on Err crates/forge_app/src/terminal_context.rs:65— `get_terminal_context` turns every `Err` into `0` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/forge_repo/src/provider/provider_repo.rs:593— `read_credentials` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Silent fallback default on Err crates/forge_select/src/preview.rs:755— `preview_content_height` turns every `Err` into `1` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the arm or in the doc comment, and the row stops firing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 7 significant file(s) lose their only recent owner: crates/forge_json_repair/src/schema_coercion.rs, crates/forge_app/src/dto/openai/copilot_model.rs, crates/forge_repo/src/provider/bedrock_sanitize_ids.rs, crates/forge_app/src/dto/openai/transformers/trim_tool_call_ids.rs, crates/forge_infra/src/auth/mcp_credentials.rs, crates/forge_repo/src/provider/bedrock_cache.rs, crates/forge_app/src/dto/openai/transformers/default_reasoning_content.rs. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/forge_main/src/sync_display.rs, crates/forge_app/src/dto/anthropic/transforms/drop_invalid_toolcalls.rs, crates/forge_infra/src/walker.rs. Pair on, review, or document these before any departure.
Duplicated predicate crates/forge_main/src/completer/input_completer.rs:74— `line.starts_with('/') || line.starts_with(':')` appears character-identically in 2 files — crates/forge_main/src/completer/input_completer.rs, crates/forge_main/src/highlighter.rs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate crates/forge_main/src/prompt.rs:190— `self.reasoning_effort && !matches!(effort, Effort::None)` appears character-identically in 2 files — crates/forge_main/src/prompt.rs, crates/forge_main/src/zsh/rprompt.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.
Subsumed condition operand crates/forge_main/src/prompt.rs:433— `actual.contains("HIGH")` can never decide this `||` — every value satisfying `actual.contains("HIGH")` also satisfies `actual.contains("HIG")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
Subsumed condition operand benchmarks/parse.ts:37— `evalName.endsWith("task.yml")` can never decide this `||` — every value satisfying `evalName.endsWith("task.yml")` also satisfies `evalName.endsWith(".yml")`, so the `||` chain is already decided by the latter. The expression is equivalent to the chain without it, which means it is wider than it reads. Delete the dead operand, or narrow the surviving one if IT is the accident.
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 (11 single-owned of 288 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; 288 of the 462 production source files in this repository met that bar). They are anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: crates/forge_app/src/transformers/drop_reasoning_only_messages.rs.
No ADRs found crates/forge_main/Cargo.toml:7— 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 `crates/forge_main/Cargo.toml` makes this repository a deployable product (line 7).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 2 of 25 project(s) overshoot their size bounds, lowering Project Cohesion to 8.4/10. The most over is `crates/forge_app` (29837 LoC, 311 module-visible types across 12 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 48 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: crates/forge_eventsource_stream/src/event_stream.rs, crates/forge_app/src/truncation/truncate_shell.rs, crates/forge_domain/src/tool_order.rs, crates/forge_markdown_stream/src/theme.rs, crates/forge_app/src/terminal_context.rs, crates/forge_markdown_stream/src/renderer.rs, crates/forge_domain/src/policies/policy.rs, crates/forge_eventsource/src/event_source.rs (and 40 more) (50 orphaned of 288 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; 288 of the 462 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
Outdated: aws-config — `aws-config` is locked at 1.13.0 but 1.13.2 is the current stable release on crates.io, and it already satisfies the `"1.8.13"` requirement declared in crates/forge_infra/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-config` and commit the updated REDACTED.
Outdated: aws-sdk-bedrockruntime — `aws-sdk-bedrockruntime` is locked at 1.153.0 but 1.155.0 is the current stable release on crates.io, and it already satisfies the `"1.129.0"` requirement declared in crates/forge_repo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-sdk-bedrockruntime` and commit the updated REDACTED.
Outdated: aws-smithy-runtime — `aws-smithy-runtime` is locked at 1.16.2 but 1.16.3 is the current stable release on crates.io, and it already satisfies the `"1.10"` requirement declared in crates/forge_repo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-smithy-runtime` and commit the updated REDACTED.
Outdated: aws-smithy-runtime-api — `aws-smithy-runtime-api` is locked at 1.19.2 but 1.21.0 is the current stable release on crates.io, and it already satisfies the `"1.11.3"` requirement declared in crates/forge_repo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-smithy-runtime-api` and commit the updated REDACTED.
Outdated: aws-smithy-types — `aws-smithy-types` is locked at 1.9.1 but 1.9.4 is the current stable release on crates.io, and it already satisfies the `"1.4.3"` requirement declared in crates/forge_repo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p aws-smithy-types` and commit the updated REDACTED.
Outdated: diesel — `diesel` is locked at 2.3.14 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.3.7"` requirement declared in crates/forge_infra/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p diesel` and commit the updated REDACTED.
Outdated: diesel_migrations — `diesel_migrations` is locked at 2.3.2 but 2.4.0 is the current stable release on crates.io, and it already satisfies the `"2.2.0"` requirement declared in crates/forge_infra/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p diesel_migrations` and commit the updated REDACTED.
Outdated: google-cloud-auth — `google-cloud-auth` is locked at 1.15.0 but 1.19.0 is the current stable release on crates.io, and it already satisfies the `"1.8.0"` requirement declared in crates/forge_infra/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p google-cloud-auth` and commit the updated REDACTED.
Outdated: html-escape — `html-escape` is locked at 0.3.0 but 0.3.1 is the current stable release on crates.io, and it already satisfies the `"0.3.0"` requirement declared in crates/forge_template/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p html-escape` and commit the updated REDACTED.
Outdated: mime — `mime` is locked at 0.3.17 but 0.3.18 is the current stable release on crates.io, and it already satisfies the `"0.3.16"` requirement declared in crates/forge_eventsource/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p mime` and commit the updated REDACTED.
Outdated: prost — `prost` is locked at 0.14.4 but 0.14.6 is the current stable release on crates.io, and it already satisfies the `"0.14.3"` requirement declared in crates/forge_repo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p prost` and commit the updated REDACTED.
Outdated: prost-types — `prost-types` is locked at 0.14.4 but 0.14.6 is the current stable release on crates.io, and it already satisfies the `"0.14.3"` requirement declared in crates/forge_repo/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p prost-types` and commit the updated REDACTED.
Outdated: syn — `syn` is locked at 3.0.9 but 3.0.10 is the current stable release on crates.io, and it already satisfies the `"3.0.0"` requirement declared in crates/forge_tool_macros/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p syn` and commit the updated REDACTED.
Outdated: sysinfo — `sysinfo` is locked at 0.40.1 but 0.40.3 is the current stable release on crates.io, and it already satisfies the `"0.40.0"` requirement declared in crates/forge_tracker/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p sysinfo` and commit the updated REDACTED.
Outdated: toml_edit — `toml_edit` is locked at 0.25.17+spec-1.1.0 but 0.25.19+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"0.25"` requirement declared in crates/forge_config/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml_edit` and commit the updated REDACTED.
Outdated: uuid — `uuid` is locked at 1.29.0 but 1.29.2 is the current stable release on crates.io, and it already satisfies the `"1.23.0"` requirement declared in crates/forge_domain/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p uuid` 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 01a1db0f-b082-7457-b9c8-febd51bff4cf · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 68 · Warnings: 324 · Recommendations: 94 · Info: 16 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 17:16 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.