Public report of continuedev/continue, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 26 October 2026, 18:25 UTC · Survey ID cd_748a5e2760094dfc93eb76e7cce85548
continuedev/continue
Measured 26 October 2026, 18:14 UTC, at code version 5522c6f
Regression: 1 dimension fell since the last survey
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
CAI scoreAt riskDown 5 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 182,523 lines of product code in 24 projects, tests not counted · Estimated rebuild effort: about 1.7 person-years · Weakest lens: Accessibility, 38
Findings by how serious they are
496 critical1377 serious270 minor
9 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 18:14 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
87of 87 dimensions measured by tools.
2113of 2143 findings point to an exact file and line, so you can open each one in the code. The other 30 concern the repository as a whole, such as missing documentation.
87dimensions across 7 lenses, read from 182,523 lines of product code in 24 projects.
continuedev/continue is rated At risk because critical security findings are open. Its score is held back because it has controls that only work with a mouse and images with no text description. It scores 43 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 38, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 2 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 3 points. Raising Accessibility to 70 would lift the score to about 46.
157 known security holes in the packages the code depends on can be used by attackers. 155 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and thirty-eight controls can't be used without a mouse. Making the controls work with a keyboard, updating the vulnerable packages and pinning each tool to an exact version would close these risks. Passing outside input through environment variables would fix the 14 pipeline steps that put outside input straight into a shell command, and the 18 places where the code runs text as code or as a command need a direct call instead. The 16 uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 182,523 lines, about €240,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Accessibility rose from 38 to 70, the lowest score rated Strong, the score would rise from 43 to about 46.
Code composition: what the lines of code are
Supporting code 0%Tests 100%
New since the last survey: 177 findings
These 177 critical or serious findings weren't in the previous survey, on 12 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Test Quality · Skipped test: CLI tool format tests skipped - no OpenAI API key packages/openai-adapters/src/test/cli-tools.test.ts
Test Quality · Skipped test: should successfully stream multi-part chat with image packages/openai-adapters/src/test/util.ts
Test Quality · Skipped test: Tool Call second message works packages/openai-adapters/src/test/util.ts
Test Quality · Skipped test: OpenAI tests skipped - no API key packages/openai-adapters/src/test/vercel-sdk.test.ts
Test Quality · Skipped test: Anthropic tests skipped - no API key packages/openai-adapters/src/test/vercel-sdk.test.ts
Test Quality · Skipped test: OpenAI comparison tests skipped - no API key packages/openai-adapters/src/test/vercel-sdk.test.ts
Test Quality · Skipped test: Anthropic comparison tests skipped - no API key packages/openai-adapters/src/test/vercel-sdk.test.ts
Test Quality · Skipped test: should make a real API call to the Continue service packages/continue-sdk/typescript/tests/continue.test.ts
Test Quality · Skipped test: should prioritize org over user / package secrets packages/config-yaml/src/__tests__/index.test.ts
Test Quality · Skipped test: should display correct panel description extensions/vscode/e2e/tests/GUI.test.ts
Test Quality · Skipped test: should display tutorial card after accepting onboarding quick start extensions/vscode/e2e/tests/GUI.test.ts
Test Quality · Skipped test: Should create a code block with the whole file when Cmd+L is pressed on an empty line extensions/vscode/e2e/tests/KeyboardShortcuts.test.ts
Test Quality · Skipped test: Should create a code block when Cmd+L is pressed on a non-empty line extensions/vscode/e2e/tests/KeyboardShortcuts.test.ts
Test Quality · Skipped test: should detect when new files are created extensions/cli/src/util/fileWatcher.test.ts
Test Quality · Skipped test: should detect when files are deleted extensions/cli/src/util/fileWatcher.test.ts
Test Quality · Skipped test: should handle SIGINT (Ctrl+C) by exiting process extensions/cli/src/util/prompt.test.ts
Test Quality · Skipped test: should output response and exit with -p flag extensions/cli/src/e2e/headless-simple.test.ts
Test Quality · Skipped test: should handle streaming responses in headless mode extensions/cli/src/e2e/headless-simple.test.ts
Test Quality · Skipped test: should work with minimal config extensions/cli/src/e2e/headless-simple.test.ts
Test Quality · Skipped test: should have /exit endpoint that returns success response extensions/cli/src/commands/serve.test.ts
Test Quality · Skipped test: should handle a string with CRLF line endings core/util/index.test.ts
Test Quality · Skipped test: should handle strings with tabs core/util/index.test.ts
Test Quality · Skipped test: returns correct intersection for single line overlap core/util/ranges.test.ts
Test Quality · Skipped test: should only re-index the changed files when changing branches core/indexing/CodebaseIndexer.test.ts
Test Quality · Skipped test: shouldn't re-index anything when changing back to original branch core/indexing/CodebaseIndexer.test.ts
Test Quality · Skipped test: should update the index and maintain expected database state, following the same processing order of results as the update method core/indexing/chunk/ChunkCodebaseIndex.test.ts
Test Quality · Skipped test: calculator docstrings core/edit/lazy/deterministic.test.ts
Test Quality · Skipped test: calculator stateless core/edit/lazy/deterministic.test.ts
Test Quality · Skipped test: gui add toggle core/edit/lazy/deterministic.test.ts
Test Quality · Skipped test: no lazy blocks in single top level class core/edit/lazy/deterministic.test.ts
Test Quality · Skipped test: should handle case where surrounding class is neglected, with lazy block surrounding core/edit/lazy/deterministic.test.ts
Test Quality · Skipped test: should include stderr output in error message when stdio command fails core/context/mcp/MCPConnection.vitest.ts
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 691 findings
These 691 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
Explicit Debt · TodoComment repeated across 10 files core/autocomplete/context/root-path-context/test/files/typescript/generators.ts
Code Duplication · Duplicated block with local edits (20 matched lines × 2 locations) packages/openai-adapters/src/apis/CometAPI.ts
Rebuild cost: about €240,000 · Estimate
Cost to rebuild
€80,000 to €400,000, for 1,341 to 4,255 hours of work, about 1.7 person-years for 1 to 4 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 43. 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: 182,523 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: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 2 points · Low effort · ADR Quality
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Raises the score by about 2 points · Medium effort · Text alternatives
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 €240,000 to build again, about 1.7 person-years of work. Its weakest lens is Accessibility, at 38 (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
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 2 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 891 lines over the last 90 days, which is about 3,614 lines a year. At that pace, the extra work comes to an estimated 0.2 to 1.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
914 modules, with 874 dependencies between them. 4 loops run through 10 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 874 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.
2 pairs of types, where a type in com.github.continuedev.continueintellijextension.editor uses a type in com.github.continuedev.continueintellijextension.
com.github.continuedev.continueintellijextension.editor uses com.github.continuedev.continueintellijextension, so a change to com.github.continuedev.continueintellijextension can break com.github.continuedev.continueintellijextension.editor, while a change to com.github.continuedev.continueintellijextension.editor can't break com.github.continuedev.continueintellijextension.
Position
Below the diagonal: com.github.continuedev.continueintellijextension.editor uses a module listed above it, which is the healthy direction.
core.config.ProfileLifecycleManager uses packages.config-yaml.src.validation, so a change to packages.config-yaml.src.validation can break core.config.ProfileLifecycleManager, while a change to core.config.ProfileLifecycleManager can't break packages.config-yaml.src.validation.
Position
Below the diagonal: core.config.ProfileLifecycleManager uses a module listed above it, which is the healthy direction.
core.nextEdit.types uses core.autocomplete.util.HelperVars, so a change to core.autocomplete.util.HelperVars can break core.nextEdit.types, while a change to core.nextEdit.types can't break core.autocomplete.util.HelperVars.
Position
Below the diagonal: core.nextEdit.types uses a module listed above it, which is the healthy direction.
core.nextEdit.types uses gui.src.components.OSRContextMenu, so a change to gui.src.components.OSRContextMenu can break core.nextEdit.types, while a change to core.nextEdit.types can't break gui.src.components.OSRContextMenu.
Position
Below the diagonal: core.nextEdit.types uses a module listed above it, which is the healthy direction.
extensions.cli.src.services.BaseService uses manual-testing-sandbox.next-edit.next-edit-7-4-sol, so a change to manual-testing-sandbox.next-edit.next-edit-7-4-sol can break extensions.cli.src.services.BaseService, while a change to extensions.cli.src.services.BaseService can't break manual-testing-sandbox.next-edit.next-edit-7-4-sol.
Position
Below the diagonal: extensions.cli.src.services.BaseService uses a module listed above it, which is the healthy direction.
extensions.vscode.src.webviewProtocol uses core.protocol.messenger, so a change to core.protocol.messenger can break extensions.vscode.src.webviewProtocol, while a change to extensions.vscode.src.webviewProtocol can't break core.protocol.messenger.
Position
Below the diagonal: extensions.vscode.src.webviewProtocol uses a module listed above it, which is the healthy direction.
core.config.ConfigHandler uses manual-testing-sandbox.next-edit.next-edit-7-4-sol, so a change to manual-testing-sandbox.next-edit.next-edit-7-4-sol can break core.config.ConfigHandler, while a change to core.config.ConfigHandler can't break manual-testing-sandbox.next-edit.next-edit-7-4-sol.
Position
Below the diagonal: core.config.ConfigHandler uses a module listed above it, which is the healthy direction.
core.config.ConfigHandler uses packages.config-yaml.src.validation, so a change to packages.config-yaml.src.validation can break core.config.ConfigHandler, while a change to core.config.ConfigHandler can't break packages.config-yaml.src.validation.
Position
Below the diagonal: core.config.ConfigHandler uses a module listed above it, which is the healthy direction.
core.config.ConfigHandler uses core.config.ProfileLifecycleManager, so a change to core.config.ProfileLifecycleManager can break core.config.ConfigHandler, while a change to core.config.ConfigHandler can't break core.config.ProfileLifecycleManager.
Position
Below the diagonal: core.config.ConfigHandler uses a module listed above it, which is the healthy direction.
extensions.vscode.src.VsCodeIde uses extensions.vscode.src.webviewProtocol, so a change to extensions.vscode.src.webviewProtocol can break extensions.vscode.src.VsCodeIde, while a change to extensions.vscode.src.VsCodeIde can't break extensions.vscode.src.webviewProtocol.
Position
Below the diagonal: extensions.vscode.src.VsCodeIde uses a module listed above it, which is the healthy direction.
extensions.vscode.src.diff.vertical.manager uses extensions.vscode.src.webviewProtocol, so a change to extensions.vscode.src.webviewProtocol can break extensions.vscode.src.diff.vertical.manager, while a change to extensions.vscode.src.diff.vertical.manager can't break extensions.vscode.src.webviewProtocol.
Position
Below the diagonal: extensions.vscode.src.diff.vertical.manager uses a module listed above it, which is the healthy direction.
core.llm uses core.protocol.messenger, so a change to core.protocol.messenger can break core.llm, while a change to core.llm can't break core.protocol.messenger.
Position
Below the diagonal: core.llm uses a module listed above it, which is the healthy direction.
core.llm uses packages.openai-adapters.src.apis.base, so a change to packages.openai-adapters.src.apis.base can break core.llm, while a change to core.llm can't break packages.openai-adapters.src.apis.base.
Position
Below the diagonal: core.llm uses a module listed above it, which is the healthy direction.
core.llm uses core.config.ConfigHandler, so a change to core.config.ConfigHandler can break core.llm, while a change to core.llm can't break core.config.ConfigHandler.
Position
Below the diagonal: core.llm uses a module listed above it, which is the healthy direction.
core.nextEdit.NextEditProvider uses core.autocomplete.util.HelperVars, so a change to core.autocomplete.util.HelperVars can break core.nextEdit.NextEditProvider, while a change to core.nextEdit.NextEditProvider can't break core.autocomplete.util.HelperVars.
Position
Below the diagonal: core.nextEdit.NextEditProvider uses a module listed above it, which is the healthy direction.
core.nextEdit.NextEditProvider uses core.nextEdit.types, so a change to core.nextEdit.types can break core.nextEdit.NextEditProvider, while a change to core.nextEdit.NextEditProvider can't break core.nextEdit.types.
Position
Below the diagonal: core.nextEdit.NextEditProvider uses a module listed above it, which is the healthy direction.
core.nextEdit.NextEditProvider uses core.config.ConfigHandler, so a change to core.config.ConfigHandler can break core.nextEdit.NextEditProvider, while a change to core.nextEdit.NextEditProvider can't break core.config.ConfigHandler.
Position
Below the diagonal: core.nextEdit.NextEditProvider uses a module listed above it, which is the healthy direction.
core.core uses core.protocol.messenger, so a change to core.protocol.messenger can break core.core, while a change to core.core can't break core.protocol.messenger.
Position
Below the diagonal: core.core uses a module listed above it, which is the healthy direction.
core.core uses extensions.cli.src.tools.types, so a change to extensions.cli.src.tools.types can break core.core, while a change to core.core can't break extensions.cli.src.tools.types.
Position
Below the diagonal: core.core uses a module listed above it, which is the healthy direction.
core.core uses core.config.ConfigHandler, so a change to core.config.ConfigHandler can break core.core, while a change to core.core can't break core.config.ConfigHandler.
Position
Below the diagonal: core.core uses a module listed above it, which is the healthy direction.
core.core uses core.nextEdit.NextEditProvider, so a change to core.nextEdit.NextEditProvider can break core.core, while a change to core.core can't break core.nextEdit.NextEditProvider.
Position
Below the diagonal: core.core uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in core.llm.llms.Bedrock uses a type in core.llm.
The types involved
core.llm.llms.Bedrock.Bedrock → core.llm.BaseLLM
Direction
core.llm.llms.Bedrock uses core.llm, so a change to core.llm can break core.llm.llms.Bedrock, while a change to core.llm.llms.Bedrock can't break core.llm.
Position
Below the diagonal: core.llm.llms.Bedrock uses a module listed above it, which is the healthy direction.
core.llm.llms.OpenAI uses extensions.cli.src.tools.types, so a change to extensions.cli.src.tools.types can break core.llm.llms.OpenAI, while a change to core.llm.llms.OpenAI can't break extensions.cli.src.tools.types.
Position
Below the diagonal: core.llm.llms.OpenAI uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in core.llm.llms.OpenAI uses a type in core.llm.
The types involved
core.llm.llms.OpenAI.OpenAI → core.llm.BaseLLM
Direction
core.llm.llms.OpenAI uses core.llm, so a change to core.llm can break core.llm.llms.OpenAI, while a change to core.llm.llms.OpenAI can't break core.llm.
Position
Below the diagonal: core.llm.llms.OpenAI uses a module listed above it, which is the healthy direction.
extensions.vscode.src.autocomplete.completionProvider uses gui.src.components.OSRContextMenu, so a change to gui.src.components.OSRContextMenu can break extensions.vscode.src.autocomplete.completionProvider, while a change to extensions.vscode.src.autocomplete.completionProvider can't break gui.src.components.OSRContextMenu.
Position
Below the diagonal: extensions.vscode.src.autocomplete.completionProvider uses a module listed above it, which is the healthy direction.
extensions.vscode.src.autocomplete.completionProvider uses extensions.vscode.src.webviewProtocol, so a change to extensions.vscode.src.webviewProtocol can break extensions.vscode.src.autocomplete.completionProvider, while a change to extensions.vscode.src.autocomplete.completionProvider can't break extensions.vscode.src.webviewProtocol.
Position
Below the diagonal: extensions.vscode.src.autocomplete.completionProvider uses a module listed above it, which is the healthy direction.
extensions.vscode.src.autocomplete.completionProvider uses core.config.ConfigHandler, so a change to core.config.ConfigHandler can break extensions.vscode.src.autocomplete.completionProvider, while a change to extensions.vscode.src.autocomplete.completionProvider can't break core.config.ConfigHandler.
Position
Below the diagonal: extensions.vscode.src.autocomplete.completionProvider uses a module listed above it, which is the healthy direction.
extensions.vscode.src.autocomplete.completionProvider uses extensions.vscode.src.VsCodeIde, so a change to extensions.vscode.src.VsCodeIde can break extensions.vscode.src.autocomplete.completionProvider, while a change to extensions.vscode.src.autocomplete.completionProvider can't break extensions.vscode.src.VsCodeIde.
Position
Below the diagonal: extensions.vscode.src.autocomplete.completionProvider uses a module listed above it, which is the healthy direction.
extensions.vscode.src.autocomplete.completionProvider uses core.nextEdit.NextEditProvider, so a change to core.nextEdit.NextEditProvider can break extensions.vscode.src.autocomplete.completionProvider, while a change to extensions.vscode.src.autocomplete.completionProvider can't break core.nextEdit.NextEditProvider.
Position
Below the diagonal: extensions.vscode.src.autocomplete.completionProvider uses a module listed above it, which is the healthy direction.
extensions.cli.src uses extensions.cli.src.permissions.types, so a change to extensions.cli.src.permissions.types can break extensions.cli.src, while a change to extensions.cli.src can't break extensions.cli.src.permissions.types.
Position
Below the diagonal: extensions.cli.src uses a module listed above it, which is the healthy direction.
extensions.cli.src uses extensions.cli.src.services.types, so a change to extensions.cli.src.services.types can break extensions.cli.src, while a change to extensions.cli.src can't break extensions.cli.src.services.types.
Position
Below the diagonal: extensions.cli.src uses a module listed above it, which is the healthy direction.
extensions.cli.src uses packages.continue-sdk.typescript.api.src.apis.DefaultApi, so a change to packages.continue-sdk.typescript.api.src.apis.DefaultApi can break extensions.cli.src, while a change to extensions.cli.src can't break packages.continue-sdk.typescript.api.src.apis.DefaultApi.
Position
Below the diagonal: extensions.cli.src uses a module listed above it, which is the healthy direction.
extensions.cli.src uses packages.openai-adapters.src.apis.base, so a change to packages.openai-adapters.src.apis.base can break extensions.cli.src, while a change to extensions.cli.src can't break packages.openai-adapters.src.apis.base.
Position
Below the diagonal: extensions.cli.src uses a module listed above it, which is the healthy direction.
extensions.cli.src uses core.llm.llms.Bedrock, so a change to core.llm.llms.Bedrock can break extensions.cli.src, while a change to extensions.cli.src can't break core.llm.llms.Bedrock.
Position
Below the diagonal: extensions.cli.src uses a module listed above it, which is the healthy direction.
extensions.cli.src.commands uses packages.openai-adapters.src.apis.base, so a change to packages.openai-adapters.src.apis.base can break extensions.cli.src.commands, while a change to extensions.cli.src.commands can't break packages.openai-adapters.src.apis.base.
Position
Below the diagonal: extensions.cli.src.commands uses a module listed above it, which is the healthy direction.
extensions.cli.src.commands uses core.llm.llms.Bedrock, so a change to core.llm.llms.Bedrock can break extensions.cli.src.commands, while a change to extensions.cli.src.commands can't break core.llm.llms.Bedrock.
Position
Below the diagonal: extensions.cli.src.commands uses a module listed above it, which is the healthy direction.
extensions.cli.src.stream uses extensions.cli.src.permissions.types, so a change to extensions.cli.src.permissions.types can break extensions.cli.src.stream, while a change to extensions.cli.src.stream can't break extensions.cli.src.permissions.types.
Position
Below the diagonal: extensions.cli.src.stream uses a module listed above it, which is the healthy direction.
extensions.cli.src.stream uses extensions.cli.src.tools.types, so a change to extensions.cli.src.tools.types can break extensions.cli.src.stream, while a change to extensions.cli.src.stream can't break extensions.cli.src.tools.types.
Position
Below the diagonal: extensions.cli.src.stream uses a module listed above it, which is the healthy direction.
extensions.cli.src.stream uses packages.openai-adapters.src.apis.base, so a change to packages.openai-adapters.src.apis.base can break extensions.cli.src.stream, while a change to extensions.cli.src.stream can't break packages.openai-adapters.src.apis.base.
Position
Below the diagonal: extensions.cli.src.stream uses a module listed above it, which is the healthy direction.
extensions.cli.src.stream uses core.llm.llms.Bedrock, so a change to core.llm.llms.Bedrock can break extensions.cli.src.stream, while a change to extensions.cli.src.stream can't break core.llm.llms.Bedrock.
Position
Below the diagonal: extensions.cli.src.stream uses a module listed above it, which is the healthy direction.
extensions.cli.src.util uses packages.openai-adapters.src.apis.base, so a change to packages.openai-adapters.src.apis.base can break extensions.cli.src.util, while a change to extensions.cli.src.util can't break packages.openai-adapters.src.apis.base.
Position
Below the diagonal: extensions.cli.src.util uses a module listed above it, which is the healthy direction.
extensions.cli.src.util uses core.llm.llms.Bedrock, so a change to core.llm.llms.Bedrock can break extensions.cli.src.util, while a change to extensions.cli.src.util can't break core.llm.llms.Bedrock.
Position
Below the diagonal: extensions.cli.src.util uses a module listed above it, which is the healthy direction.
extensions.vscode.src uses core.config.ConfigHandler, so a change to core.config.ConfigHandler can break extensions.vscode.src, while a change to extensions.vscode.src can't break core.config.ConfigHandler.
Position
Below the diagonal: extensions.vscode.src uses a module listed above it, which is the healthy direction.
extensions.vscode.src uses extensions.vscode.src.VsCodeIde, so a change to extensions.vscode.src.VsCodeIde can break extensions.vscode.src, while a change to extensions.vscode.src can't break extensions.vscode.src.VsCodeIde.
Position
Below the diagonal: extensions.vscode.src uses a module listed above it, which is the healthy direction.
extensions.vscode.src uses extensions.vscode.src.diff.vertical.manager, so a change to extensions.vscode.src.diff.vertical.manager can break extensions.vscode.src, while a change to extensions.vscode.src can't break extensions.vscode.src.diff.vertical.manager.
Position
Below the diagonal: extensions.vscode.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in extensions.vscode.src uses a type in core.core.
The types involved
extensions.vscode.src.commands → core.core.Core
Direction
extensions.vscode.src uses core.core, so a change to core.core can break extensions.vscode.src, while a change to extensions.vscode.src can't break core.core.
Position
Below the diagonal: extensions.vscode.src uses a module listed above it, which is the healthy direction.
extensions.vscode.src.extension.VsCodeExtension uses extensions.vscode.src.webviewProtocol, so a change to extensions.vscode.src.webviewProtocol can break extensions.vscode.src.extension.VsCodeExtension, while a change to extensions.vscode.src.extension.VsCodeExtension can't break extensions.vscode.src.webviewProtocol.
Position
Below the diagonal: extensions.vscode.src.extension.VsCodeExtension uses a module listed above it, which is the healthy direction.
extensions.vscode.src.extension.VsCodeExtension uses core.config.ConfigHandler, so a change to core.config.ConfigHandler can break extensions.vscode.src.extension.VsCodeExtension, while a change to extensions.vscode.src.extension.VsCodeExtension can't break core.config.ConfigHandler.
Position
Below the diagonal: extensions.vscode.src.extension.VsCodeExtension uses a module listed above it, which is the healthy direction.
extensions.vscode.src.extension.VsCodeExtension uses extensions.vscode.src.VsCodeIde, so a change to extensions.vscode.src.VsCodeIde can break extensions.vscode.src.extension.VsCodeExtension, while a change to extensions.vscode.src.extension.VsCodeExtension can't break extensions.vscode.src.VsCodeIde.
Position
Below the diagonal: extensions.vscode.src.extension.VsCodeExtension uses a module listed above it, which is the healthy direction.
extensions.vscode.src.extension.VsCodeExtension uses extensions.vscode.src.diff.vertical.manager, so a change to extensions.vscode.src.diff.vertical.manager can break extensions.vscode.src.extension.VsCodeExtension, while a change to extensions.vscode.src.extension.VsCodeExtension can't break extensions.vscode.src.diff.vertical.manager.
Position
Below the diagonal: extensions.vscode.src.extension.VsCodeExtension uses a module listed above it, which is the healthy direction.
extensions.vscode.src.extension.VsCodeExtension uses core.core, so a change to core.core can break extensions.vscode.src.extension.VsCodeExtension, while a change to extensions.vscode.src.extension.VsCodeExtension can't break core.core.
Position
Below the diagonal: extensions.vscode.src.extension.VsCodeExtension uses a module listed above it, which is the healthy direction.
extensions.vscode.src.extension.VsCodeExtension uses extensions.vscode.src.autocomplete.completionProvider, so a change to extensions.vscode.src.autocomplete.completionProvider can break extensions.vscode.src.extension.VsCodeExtension, while a change to extensions.vscode.src.extension.VsCodeExtension can't break extensions.vscode.src.autocomplete.completionProvider.
Position
Below the diagonal: extensions.vscode.src.extension.VsCodeExtension uses a module listed above it, which is the healthy direction.
packages.openai-adapters.src.apis.OpenAI uses packages.openai-adapters.src.apis.base, so a change to packages.openai-adapters.src.apis.base can break packages.openai-adapters.src.apis.OpenAI, while a change to packages.openai-adapters.src.apis.OpenAI can't break packages.openai-adapters.src.apis.base.
Position
Below the diagonal: packages.openai-adapters.src.apis.OpenAI uses a module listed above it, which is the healthy direction.
packages.openai-adapters.src.apis.OpenAI uses core.llm.llms.OpenAI, so a change to core.llm.llms.OpenAI can break packages.openai-adapters.src.apis.OpenAI, while a change to packages.openai-adapters.src.apis.OpenAI can't break core.llm.llms.OpenAI.
Position
Below the diagonal: packages.openai-adapters.src.apis.OpenAI uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 61% · Adequate · gated by D2, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
258
High / Critical
A03:2025 — Software Supply Chain Failures
255
High / Critical
A02:2025 — Security Misconfiguration
15
High / Critical
A07:2025 — Authentication Failures
6
High / Critical
Roadmap
First, ensure all interactive controls are fully keyboard-accessible and links use proper hrefs, while adding descriptive text alternatives for all images, media, and canvas elements. Next, integrate accessibility checks into the development toolchain by adding linting rules, test assertions, and CI gates to prevent future regressions. Finally, resolve architectural issues by fixing cross-package import violations and breaking circular dependencies to improve code stability and maintainability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Resolve the 7 Orphaned knowledge finding(s) in Knowledge Freshness — start with NextEditWindowManager.kt, next-edit-10-5-sol.ts, evaluateTerminalCommandSecurity.ts.
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 — 496
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 — 1377
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 — 270
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 9
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 87 of 87 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 87 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, 2113 of 2143 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 4,895 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries test source in .rs that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 5 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares 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.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D31 IaC & Container Security — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Extensions/vscode/textmate-syntaxes/Dockerfile.tmLanguage carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 2 of 3 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `core/llm/openaiTypeConverters.ts`, `extensions/cli/src/services/index.ts`, `extensions/cli/src/ui/components/MemoizedMessage.tsx`, `extensions/cli/src/ui/hooks/useChat.helpers.ts`, `extensions/cli/src/ui/hooks/useChat.imageProcessing.ts`, … (+3 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC4 Keyboard semantics — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 31 further occurrence(s) are not listed individually; the score already reflects all 71.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — #1 transferring dockerfile: 3.35kB done #1 DONE 0.0s REDACTED:1 -------------------- 1 | >>> <?xml version="1.0" encoding="UTF-8"?> 2 | <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> 3 | <plist version="1.0"> -------------------- ERROR: failed to solve: dockerfile parse error on line 1: unknown instruction: <?xml; runtime evidence skipped.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P2 Observability — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 369 further occurrence(s) are not listed individually; the score already reflects all 409.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
PF3 Async & latency hygiene — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 96 further occurrence(s) are not listed individually; the score already reflects all 136.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 312 further occurrence(s) are not listed individually; the score already reflects all 352.
R11 Import Boundaries — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 118 further occurrence(s) are not listed individually; the score already reflects all 158.
R3 Large Files — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 50 further occurrence(s) are not listed individually; the score already reflects all 90.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 101 further occurrence(s) are not listed individually; the score already reflects all 141.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 204 further occurrence(s) are not listed individually; the score already reflects all 244.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 64 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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 REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
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.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
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.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
170 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Core.registerMessageHandlers at 70. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being callTool.callBuiltInTool at 18 — they are counted neither in the figure above nor in this dimension's score.
+ 160 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Core.registerMessageHandlers (cyclomatic 70), ContinueCompletionProvider.provideInlineCompletionItems (cyclomatic 61). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 5.9 to about 6.1/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 270 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with runTerminalCommand.runTerminalCommandImpl (cognitive 152). — Refactoring it lifts Cognitive Complexity from 2.8 to about 3.3/10.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.3 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 71 FunctionTooLong finding(s) in God Classes — start with index.tsx (5), useChat.ts (2), ToolsSection.tsx (2). — One of this dimension's main actionable groups (71 warning-level).
Resolve the 19 FileTooLong finding(s) in God Classes — start with REDACTED, index.ts, core.ts. — One of this dimension's main actionable groups (19 warning-level).
Resolve the 13 MethodTooLong finding(s) in God Classes — start with core.ts, completionProvider.ts, REDACTED. — One of this dimension's main actionable groups (13 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
8 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 1 of the 9 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .ts, .tsx (91% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with GitService.kt, continue_tutorial.java. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (18 lines × 2) finding(s) in Code Duplication — start with continue_tutorial.py, lib.rs. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Edited copy of a member (23 corresponding lines) finding(s) in Code Duplication — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.3 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
24 production modules (Gradle+Cargo+npm+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 5 module(s) off the main sequence, with abstractness counted on 16 of the 24 (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: @continuedev/fetch · ×5
What to do
Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with VsCodeIde.ts, ideUtils.ts, ChatHistoryService.ts. — One of this dimension's main actionable groups (4 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage8.8 / 10Strong✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 51.9% — 161 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest in binary/: not run; jest in core/: not run; vitest + @vitest/coverage-v8 via `npm ci --ignore-scripts` in gui/; jest in packages/config-yaml/: not run; jest in packages/continue-sdk/typescript/: not run).
Resolve the 161 Low coverage finding(s) in Code Coverage — start with index.tsx (4), Layout.tsx (2), utils.ts (2). — One of this dimension's main actionable groups (161 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution9.6 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
4928 test methods: 4781 unit, 14 integration, 0 BDD, 133 e2e. The JavaScript/TypeScript suite contributes 4895 `it`/`test` case(s) across 423 test file(s) declaring at least one; its tier split is read from package names and paths only. The Rust suite contributes 17 `#[test]` function(s) across 6 file(s) declaring at least one; its unit/integration split is Cargo's own — 0 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 16 test function(s) across 16 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.8 / 10Stronggated by 56 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
35 skipped (3 with a documented reason), 23 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4895 tests. Measured on the JavaScript/TypeScript suite only — test source in .rs went unread, so its test quality is unmeasured and is not in these counts.
Skipped test: CLI tool format tests skipped - no OpenAI API key · ×32packages/openai-adapters/src/test/cli-tools.test.ts:131
No assertions: Skipping API key tests · ×23packages/openai-adapters/src/test/main.test.ts:202
Fixed-sleep synchronisation: GitDiffCache refreshes cache after expirationcore/autocomplete/snippets/gitDiffCache.vitest.ts:22
Mock-dominated test: should handle edit mode apply state updates · ×45gui/src/redux/thunks/handleApplyStateUpdate.test.ts:92
Resolve the 32 Skipped test finding(s) in Test Quality — start with deterministic.test.ts (5), vercel-sdk.test.ts (4), index.test.ts (3). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 23 No assertions finding(s) in Test Quality — start with GUI.test.ts (7), TUIChat.dualModeHelper.tsx (3), SSH.skip.ts (2). — One of this dimension's main actionable groups (23 warning-level).
Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with gitDiffCache.vitest.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in binary/ (6 tests); jest via `npm ci --ignore-scripts` in core/ (0 tests); vitest via `npm ci --ignore-scripts` in extensions/cli/ (1091 tests); vitest via `npm ci --ignore-scripts` in extensions/vscode/ (55 tests); vitest via `npm ci --ignore-scripts` in gui/ (353 tests); jest via `npm ci --ignore-scripts` in packages/config-yaml/ (0 tests); jest via `npm ci --ignore-scripts` in packages/continue-sdk/typescript/ (0 tests); vitest via `npm ci --ignore-scripts` in packages/fetch/ (97 tests); vitest via `npm ci --ignore-scripts` in packages/openai-adapters/ (145 tests); vitest via `npm ci --ignore-scripts` in packages/terminal-security/ (224 tests)): measured (0 flaky).
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 141 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json and a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
62 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is extensions/vscode/src/activation/NextEditWindowManager.ts. Counted over 630 of the 1365 production source files in this repository: 732 are under the ~2,400-byte size floor this dimension measures over, and the remaining 3 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×4
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.
187 deducted task-comment markers across 177582 LoC (0.1/KLoC) → score 9.8. 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 144 TodoComment finding(s) in Explicit Debt — start with Bedrock.ts (6), core.ts (5), index.test.ts (4). — One of this dimension's main actionable groups (144 warning-level).
Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with UriUtilsTest.kt, InlineEditPanel.kt, CodebaseIndexer.ts. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 TodoComment repeated across 10 files finding(s) in Explicit Debt — start with types.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 174 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
258 finding(s): 0 critical, 221 high, 37 medium, 0 low. 135 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 14 file(s) — `core/llm/openaiTypeConverters.ts` (line 465, line 489, line 514, …), `core/util/start_ollama.sh` (line 44), `extensions/cli/src/services/index.ts` (line 391), `extensions/cli/src/ui/components/MemoizedMessage.tsx` (line 15), `extensions/cli/src/ui/hooks/useChat.helpers.ts` (line 176), … (+9 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 17 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
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 20 REDACTED finding(s) charged to Static Analysis (SAST) — the other 135 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (155 issue-level, 20 of them charged here).
Resolve the 18 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (18 issue-level).
Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (14 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 125 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (121), REDACTED (4). — One of this dimension's main actionable groups (125 issue-level).
Resolve the 26 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21), REDACTED (5). — One of this dimension's main actionable groups (26 issue-level).
Resolve the 5 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 8 High IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
114 of 633 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditWindowManager.kt. Counted over 633 of the 1365 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 7 Orphaned knowledge finding(s) in Knowledge Freshness — start with NextEditWindowManager.kt, next-edit-10-5-sol.ts, evaluateTerminalCommandSecurity.ts. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 107 Orphaned file finding(s) in Knowledge Freshness — start with NextEditJumpManager.kt, next-edit-6-3-sol.ts, node-fetch-patch.js. — One of this dimension's main actionable groups (107 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 17 Change coupling finding(s) in Change Coupling — start with core.ts (2), ideWebview.ts (2), builtIn.ts. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with ide.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with core.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 43 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.
End-of-life runtime: Node.js 20.nvmrc:1
What to do
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives3.3 / 10Weak✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×8) — gui/src/components/SafeImg.tsx:52, gui/src/components/loaders/Loader.tsx:31, gui/src/components/modelSelection/ModelCard.tsx:135, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.2 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label. (×7) — docs-site/components/docs/DocsShell.tsx:369, gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/InsertButton.tsx:19, gui/src/components/gui/Switch.tsx:39, …
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — gui/src/components/DeprecationBanner.tsx:46
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×5) — gui/src/components/History/index.tsx:152, gui/src/components/modelSelection/ModelSelectionListbox.tsx:135, gui/src/pages/config/components/UserSetting.tsx:165, …
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×4) — gui/src/components/OnboardingCard/components/OnboardingCardTabs.tsx:68, gui/src/pages/config/components/UserSetting.tsx:79, gui/src/pages/config/components/UserSetting.tsx:196, …
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×6) — gui/src/components/OnboardingCard/components/OnboardingProvidersTab.tsx:69, gui/src/forms/AddModelForm.tsx:194, gui/src/forms/AddModelForm.tsx:225, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
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>. (×2) — docs-site/app/layout.tsx:20, manual-testing-sandbox/test.html:2
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — gui/src/components/History/index.tsx:188
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 interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×38) — docs-site/components/docs/DocsShell.tsx:369, gui/src/components/ConversationStarters/ConversationStarterCard.tsx:14, gui/src/components/ConversationStarters/ConversationStarterCards.tsx:56, …
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. — REDACTED:521
A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM). — gui/src/components/console/List.tsx:33
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×3) — gui/src/components/History/index.tsx:152, gui/src/components/modelSelection/ModelSelectionListbox.tsx:135, gui/src/styles/ThemePage.tsx:134
<select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — gui/src/components/OnboardingCard/components/OnboardingCardTabs.tsx:68
<button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/ApplyActions.tsx:70, gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/CreateFileButton.tsx:14
`*:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — gui/src/index.css:53
`.wmde-markdown .anchor:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — gui/src/components/StyledMarkdownPreview/markdown.css:570
`textarea:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — gui/src/components/mainInput/AtMentionDropdown/index.tsx:129
`span::after` moves (`animation: ____________________ 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — gui/src/components/AnimatedEllipsis.tsx:19
`.css-in-js` moves (`animation: ________ 3s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — gui/src/components/loaders/BlinkingDot.tsx:16
`span::after` moves (`animation: ______________ 1s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — REDACTED:22
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.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 247 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
`@continuedev/core` is a Domain project but references `@continuedev/openai-adapters`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one. — core/package.json:65
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`DefaultApiInterface` declares 16 required operations: `getAssistantRaw`, `getAssistant`, `getFreeTrialStatusRaw`, `getFreeTrialStatus`, `getModelsAddOnCheckoutUrlRaw`, `getModelsAddOnCheckoutUrl`, `getPolicyRaw`, `getPolicy`, `listAssistantFullSlugsRaw`, `listAssistantFullSlugs`, `listAssistantsRaw`, `listAssistants`, `listOrganizationsRaw`, `listOrganizations`, `syncSecretsRaw`, `syncSecrets`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/continue-sdk/typescript/api/src/apis/DefaultApi.ts:87
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
gui.src.components.mainInput.InputToolbar.ToolbarOptions's [enterText, hideAddContext, hideImageUpload, hideSelectModel, hideUseCodebase] are judged in gui.src.components.mainInput.InputToolbar, gui.src.components.mainInput.TipTapEditor.TipTapEditor — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
manual-testing-sandbox.next-edit.next-edit-10-5-sol.Task's [assignedTo, createdBy] are judged in manual-testing-sandbox.next-edit.next-edit-10-5-sol.InMemoryTaskRepository, manual-testing-sandbox.next-edit.next-edit-10-5-sol.TaskAuthorizationService — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
What to do
Move each repeated judgement onto the type that owns the members it reads, so the rule has one home and cannot drift.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 14 of 26 project(s) that lack one — worth up to 1.1 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
docs/guides/github-mcp-continue-cookbook.mdx names Node.js 22, but the repository declares engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, pinned 20. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/github-mcp-continue-cookbook.mdx:24
docs/guides/netlify-mcp-continuous-deployment.mdx names Node.js 22, but the repository declares engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, pinned 20. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/guides/netlify-mcp-continuous-deployment.mdx:46
extensions/vscode/README.md links to `docs/images/agent.gif`, but `extensions/vscode/docs/images/agent.gif` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — extensions/vscode/README.md:30
extensions/vscode/README.md links to `docs/images/chat.gif`, but `extensions/vscode/docs/images/chat.gif` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — extensions/vscode/README.md:36
extensions/vscode/README.md links to `docs/images/edit.gif`, but `extensions/vscode/docs/images/edit.gif` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — extensions/vscode/README.md:42
extensions/vscode/README.md links to `docs/images/autocomplete.gif`, but `extensions/vscode/docs/images/autocomplete.gif` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — extensions/vscode/README.md:48
What to do
Reconcile the README with reality: docs/guides/github-mcp-continue-cookbook.mdx names Node.js 22, but the repository declares engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, pinned 20; docs/guides/netlify-mcp-continuous-deployment.mdx names Node.js 22, but the repository declares engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, pinned 20; extensions/vscode/README.md links to `docs/images/agent.gif`, but `extensions/vscode/docs/images/agent.gif` does not exist; extensions/vscode/README.md links to `docs/images/chat.gif`, but `extensions/vscode/docs/images/chat.gif` does not exist; extensions/vscode/README.md links to `docs/images/edit.gif`, but `extensions/vscode/docs/images/edit.gif` does not exist.
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 & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
212/224 types (95%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Kotlin: `internal`) so internals can change without breaking consumers.
Do you agree with this assessment?
P2 · Observability7.2 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 5/13 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`, `.`, `binary`, `docs-site` and 3 more.
`manual-testing-sandbox/next-edit/next-edit-1-1-sol.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-1-1-sol.ts:42
`manual-testing-sandbox/next-edit/next-edit-1-1.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-1-1.ts:29
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 455 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:455
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 462 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:462
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 469 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:469
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 483 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:483
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 953 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:953
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 963 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:963
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 970 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:970
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 978 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:978
`manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 980 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:980
`manual-testing-sandbox/next-edit/next-edit-10-5.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5.ts:28
`manual-testing-sandbox/next-edit/next-edit-10-5.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5.ts:40
`manual-testing-sandbox/next-edit/next-edit-10-5.ts` reports through `console.*` at line 89 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5.ts:89
`manual-testing-sandbox/next-edit/next-edit-10-5.ts` reports through `console.*` at line 154 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-10-5.ts:154
`manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts` reports through `console.*` at line 95 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts:95
`manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts` reports through `console.*` at line 97 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts:97
`manual-testing-sandbox/next-edit/next-edit-2-1.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-2-1.ts:53
`manual-testing-sandbox/next-edit/next-edit-2-1.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-2-1.ts:55
`manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts` reports through `console.*` at line 109 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts:109
`manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts:110
`manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts` reports through `console.*` at line 111 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts:111
`manual-testing-sandbox/next-edit/next-edit-3-2.ts` reports through `console.*` at line 98 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-3-2.ts:98
`manual-testing-sandbox/next-edit/next-edit-3-2.ts` reports through `console.*` at line 99 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-3-2.ts:99
`manual-testing-sandbox/next-edit/next-edit-3-2.ts` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-3-2.ts:100
`manual-testing-sandbox/next-edit/next-edit-4-2-sol.ts` reports through `console.*` at line 169 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-4-2-sol.ts:169
`manual-testing-sandbox/next-edit/next-edit-4-2-sol.ts` reports through `console.*` at line 171 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-4-2-sol.ts:171
`manual-testing-sandbox/next-edit/next-edit-4-2.ts` reports through `console.*` at line 148 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-4-2.ts:148
`manual-testing-sandbox/next-edit/next-edit-4-2.ts` reports through `console.*` at line 150 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-4-2.ts:150
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 89 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:89
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 95 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:95
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 128 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:128
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 210 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:210
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 218 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:218
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 248 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:248
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 254 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:254
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 259 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:259
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 260 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:260
`manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts` reports through `console.*` at line 261 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:261
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Dependabot is configured but does not watch `npm`, `cargo`, `pip`, `gradle` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`fs.copyFileSync` in `downloadNodeSqlite` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/bundle-binary.js:31
`fs.unlinkSync` in `downloadNodeSqlite` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/bundle-binary.js:40
`fs.mkdirSync` in `bundleForBinary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/bundle-binary.js:48
`fs.copyFileSync` in `bundleForBinary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/bundle-binary.js:56
`fs.writeFileSync` in `bundleForBinary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/bundle-binary.js:68
`fs.writeFileSync` in `downloadFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/ripgrep.js:35
`fs.writeFileSync` in `extractArchive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/ripgrep.js:61
`fs.mkdirSync` in `downloadRipgrep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/ripgrep.js:90
`fs.chmodSync` in `downloadRipgrep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — binary/utils/ripgrep.js:106
`fs.cpSync` in `testRootPathContext` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/autocomplete/context/root-path-context/test/testUtils.ts:58
`fs.readFileSync` in `testRootPathContext` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/autocomplete/context/root-path-context/test/testUtils.ts:66
`execSync` in `buildConfigTsWithBinary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/config/load.ts:737
`fs.existsSync` in `buildConfigTsandReadConfigJs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/config/load.ts:767
`fs.readFileSync` in `buildConfigTsandReadConfigJs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/config/load.ts:771
`fs.existsSync` in `doLoadConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — core/config/profile/doLoadConfig.ts:90, core/config/profile/doLoadConfig.ts:110
`execSync` in `getWorkspaceDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:135
`fs.existsSync` in `get` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — core/data/devdataSqlite.ts:77, core/indexing/refreshIndex.ts:93
`fs.writeFileSync` in `logLocalData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/data/log.ts:95
`fs.existsSync` in `logToOneDestination` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/data/log.ts:223
`fs.mkdirSync` in `logToOneDestination` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/data/log.ts:224
`fs.writeFileSync` in `logToOneDestination` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/data/log.ts:228
`fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — core/test/jest.global-setup.ts:8, core/test/vitest.global-setup.ts:8
`fs.rmSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — core/test/jest.global-setup.ts:9, core/test/vitest.global-setup.ts:9
`fs.statSync` in `getFileStats` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/filesystem.ts:87
`fs.readdirSync` in `listDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/filesystem.ts:106
`fs.readFileSync` in `generate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/generateRepoMap.ts:154
`fs.existsSync` in `shareSession` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/historyUtils.ts:94
`fs.mkdirSync` in `shareSession` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/historyUtils.ts:95
`fs.existsSync` in `migrate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/paths.ts:312
`fs.writeFileSync` in `migrate` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/paths.ts:316
`fs.existsSync` in `getQueryForFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/treeSitter.ts:191
`fs.readFileSync` in `getQueryForFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — core/util/treeSitter.ts:194
`fs.existsSync` in `loadMdxFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — docs-site/lib/docs.ts:83, docs-site/lib/docs.ts:89
`fs.existsSync` in `loadRawMdxFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — docs-site/lib/docs.ts:108
`fs.readFileSync` in `loadRawMdxFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — docs-site/lib/docs.ts:110
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.
51 duplicated blocks under the repository root have copies in at least two of the sibling directories binary, core, docs-site, extensions, gui, packages (+1 more sibling(s) not listed) — 34 of them are reported below, and 17 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 51 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 51 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 51 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — core/llm/llms/gemini-types.ts:1
9 duplicated blocks under packages/ have copies in at least two of the sibling directories config-types, config-yaml, openai-adapters — 4 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/config-types/src/index.ts:22
7 duplicated blocks under gui/src/ have copies in at least two of the sibling directories components, context, hooks, pages, redux — 2 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — gui/src/context/MockIdeMessenger.ts:49
6 duplicated blocks under core/ have copies in at least two of the sibling directories autocomplete, config, context, nextEdit, promptFiles — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — core/autocomplete/CompletionProvider.ts:66
6 duplicated blocks under packages/config-yaml/src/schemas/data/ have copies in at least two of the sibling directories autocomplete, chatFeedback, chatInteraction, editInteraction, editOutcome, nextEditOutcome (+2 more sibling(s) not listed) — 2 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/config-yaml/src/schemas/data/autocomplete/v0.1.0.ts:23
REDACTED:14 · REDACTED:14 — these 2 files are line-for-line copies of one another — 291 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — REDACTED:14
core/llm/llms/gemini-types.ts:1 · packages/openai-adapters/src/util/gemini-types.ts:1 — these 2 files are line-for-line copies of one another — 268 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — core/llm/llms/gemini-types.ts:1
manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts:5 · manual-testing-sandbox/next-edit/next-edit-6-3.ts:5 — the two spans are one implementation copied and then locally edited — 697 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts:5
core/nextEdit/providers/InstinctNextEditProvider.ts:16 · core/nextEdit/providers/MercuryCoderNextEditProvider.ts:17 — the two spans are one implementation copied and then locally edited — 457 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/nextEdit/providers/InstinctNextEditProvider.ts:16
core/autocomplete/CompletionProvider.ts:66 · core/nextEdit/NextEditProvider.ts:130 — the two spans are one implementation copied and then locally edited — 526 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/autocomplete/CompletionProvider.ts:66
extensions/vscode/scripts/prepackage.js:193 · extensions/vscode/scripts/utils.js:117 — the two spans are one implementation copied and then locally edited — 403 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extensions/vscode/scripts/prepackage.js:193
extensions/cli/src/ui/components/ChatScreenContent.tsx:14 · extensions/cli/src/ui/components/ScreenContent.tsx:32 — the two spans are one implementation copied and then locally edited — 269 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extensions/cli/src/ui/components/ChatScreenContent.tsx:14
core/llm/llms/Anthropic.ts:132 · packages/openai-adapters/src/apis/Anthropic.ts:163 — the two spans are one implementation copied and then locally edited — 295 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/llm/llms/Anthropic.ts:132
core/context/retrieval/pipelines/NoRerankerRetrievalPipeline.ts:19 · core/context/retrieval/pipelines/RerankerRetrievalPipeline.ts:16 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — core/context/retrieval/pipelines/NoRerankerRetrievalPipeline.ts:19
core/llm/llms/Inception.ts:70 · packages/openai-adapters/src/apis/Inception.ts:109 — the two spans are one implementation copied and then locally edited — 319 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/llm/llms/Inception.ts:70
binary/src/IpcMessenger.ts:29 · binary/src/TcpMessenger.ts:65 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — binary/src/IpcMessenger.ts:29
packages/config-types/src/index.ts:22 · packages/config-yaml/src/schemas/models.ts:3 — the two spans are one implementation copied and then locally edited — 480 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/config-types/src/index.ts:22
core/autocomplete/util/AutocompleteLoggingService.ts:41 · core/nextEdit/NextEditLoggingService.ts:112 — the two spans are one implementation copied and then locally edited — 319 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/autocomplete/util/AutocompleteLoggingService.ts:41
core/autocomplete/templating/AutocompleteTemplate.ts:179 · core/autocomplete/templating/AutocompleteTemplate.ts:237 — the two spans are one implementation copied and then locally edited — 242 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/autocomplete/templating/AutocompleteTemplate.ts:179
core/llm/llms/Bedrock.ts:467 · packages/openai-adapters/src/apis/Bedrock.ts:282 — the two spans are one implementation copied and then locally edited — 212 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/llm/llms/Bedrock.ts:467
packages/openai-adapters/src/apis/AiSdk.ts:101 · packages/openai-adapters/src/apis/AiSdk.ts:186 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/openai-adapters/src/apis/AiSdk.ts:101
core/llm/templates/edit/codestral.ts:4 · core/llm/templates/edit/gpt.ts:4 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — core/llm/templates/edit/codestral.ts:4
core/llm/llms/Asksage.ts:262 · core/llm/llms/Asksage.ts:338 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core/llm/llms/Asksage.ts:262
extensions/cli/src/tools/edit.ts:148 · extensions/cli/src/tools/multiEdit.ts:137 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — extensions/cli/src/tools/edit.ts:148
extensions/cli/src/ui/hooks/useChat.ts:540 · extensions/cli/src/ui/hooks/useChat.ts:607 — 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. — extensions/cli/src/ui/hooks/useChat.ts:540
core/llm/index.ts:656 · core/llm/index.ts:786 · core/llm/index.ts:894 — 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. — core/llm/index.ts:656
gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx:5 · gui/src/pages/config/sections/HelpSection.tsx:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx:5
gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx:68 · gui/src/pages/config/sections/HelpSection.tsx:84 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx:68
REDACTED:35 · REDACTED:97 — the two spans are one implementation copied and then locally edited — 249 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:35
extensions/cli/src/ui/EditMessageSelector.tsx:189 · extensions/cli/src/ui/UserInput.tsx:808 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — extensions/cli/src/ui/EditMessageSelector.tsx:189
gui/src/components/modelSelection/ModelSelectionListbox.tsx:158 · gui/src/components/modelSelection/ModelSelectionListbox.tsx:203 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — gui/src/components/modelSelection/ModelSelectionListbox.tsx:158
packages/openai-adapters/src/apis/OpenRouterCaching.ts:181 · packages/openai-adapters/src/apis/OpenRouterCaching.ts:239 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/openai-adapters/src/apis/OpenRouterCaching.ts:181
core/llm/llms/SageMaker.ts:39 · core/llm/llms/SageMaker.ts:87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — core/llm/llms/SageMaker.ts:39
extensions/cli/src/ui/ConfigSelector.tsx:24 · extensions/cli/src/ui/ModelSelector.tsx:17 — the two spans are one implementation copied and then locally edited — 204 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — extensions/cli/src/ui/ConfigSelector.tsx:24
core/llm/llms/Deepseek.ts:26 · core/llm/llms/LlamaStack.ts:23 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — core/llm/llms/Deepseek.ts:26
core/llm/llms/Docker.ts:171 · core/llm/llms/Ollama.ts:770 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/llm/llms/Docker.ts:171
REDACTED:207 · REDACTED:242 — 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. — REDACTED:207
gui/src/pages/stats.tsx:70 · gui/src/pages/stats.tsx:102 — 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. — gui/src/pages/stats.tsx:70
core/indexing/LanceDbIndex.ts:500 · core/indexing/chunk/ChunkCodebaseIndex.ts:206 — the two spans are one implementation copied and then locally edited — 185 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/indexing/LanceDbIndex.ts:500
core/llm/llms/OpenAI.ts:655 · core/llm/llms/SiliconFlow.ts:23 — the two spans are one implementation copied and then locally edited — 162 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/llm/llms/OpenAI.ts:655
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
binary/build.js:6 reaches into another package with a relative path (../scripts/util) — import the package by name instead. — binary/build.js:6
binary/build.js:11 reaches into another package with a relative path (../extensions/vscode/scripts/install-copy-nodemodule) — import the package by name instead. — binary/build.js:11
binary/utils/bundle-binary.js:8 reaches into another package with a relative path (../../scripts/util) — import the package by name instead. — binary/utils/bundle-binary.js:8
binary/utils/bundle-binary.js:14 reaches into another package with a relative path (../../extensions/vscode/scripts/download-copy-sqlite) — import the package by name instead. — binary/utils/bundle-binary.js:14
core/autocomplete/CompletionProvider.ts:2 reaches into another package with a relative path (../index.js) — import the package by name instead. — core/autocomplete/CompletionProvider.ts:2
core/autocomplete/postprocessing/index.ts:4 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/autocomplete/postprocessing/index.ts:4
core/autocomplete/templating/AutocompleteTemplate.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/autocomplete/templating/AutocompleteTemplate.ts:3
core/autocomplete/templating/index.ts:7 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/autocomplete/templating/index.ts:7
core/commands/slash/built-in-legacy/cmd.ts:2 reaches into another package with a relative path (../../../index.js) — import the package by name instead. — core/commands/slash/built-in-legacy/cmd.ts:2
core/commands/slash/built-in-legacy/commit.ts:1 reaches into another package with a relative path (../../../index.js) — import the package by name instead. — core/commands/slash/built-in-legacy/commit.ts:1
core/commands/slash/built-in-legacy/http.ts:2 reaches into another package with a relative path (../../../index.js) — import the package by name instead. — core/commands/slash/built-in-legacy/http.ts:2
core/commands/slash/built-in-legacy/review.ts:1 reaches into another package with a relative path (../../../index.js) — import the package by name instead. — core/commands/slash/built-in-legacy/review.ts:1
core/commands/slash/built-in-legacy/share.ts:4 reaches into another package with a relative path (../../../index.js) — import the package by name instead. — core/commands/slash/built-in-legacy/share.ts:4
core/commands/slash/mcpSlashCommand.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/commands/slash/mcpSlashCommand.ts:3
core/config/ConfigHandler.ts:3 reaches into another package with a relative path (../index.js) — import the package by name instead. — core/config/ConfigHandler.ts:3
core/config/ProfileLifecycleManager.ts:7 reaches into another package with a relative path (../index.js) — import the package by name instead. — core/config/ProfileLifecycleManager.ts:7
core/config/profile/IProfileLoader.ts:4 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/config/profile/IProfileLoader.ts:4
core/config/profile/LocalProfileLoader.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/config/profile/LocalProfileLoader.ts:3
core/context/index.ts:1 reaches into another package with a relative path (../index.js) — import the package by name instead. — core/context/index.ts:1
core/context/providers/CodeContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/CodeContextProvider.ts:1
core/context/providers/DatabaseContextProvider.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/DatabaseContextProvider.ts:3
core/context/providers/DebugLocalsProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/DebugLocalsProvider.ts:1
core/context/providers/DiffContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/DiffContextProvider.ts:1
core/context/providers/DiscordContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/DiscordContextProvider.ts:1
core/context/providers/FileTreeContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/FileTreeContextProvider.ts:1
core/context/providers/FolderContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/FolderContextProvider.ts:1
core/context/providers/GitCommitContextProvider.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/GitCommitContextProvider.ts:3
core/context/providers/GitHubIssuesContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/GitHubIssuesContextProvider.ts:1
REDACTED:3 reaches into another package with a relative path (../../index.js) — import the package by name instead. — REDACTED:3
core/context/providers/GoogleContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/GoogleContextProvider.ts:1
REDACTED:5 reaches into another package with a relative path (../../index.js) — import the package by name instead. — REDACTED:5
core/context/providers/HttpContextProvider.ts:2 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/HttpContextProvider.ts:2
core/context/providers/JiraIssuesContextProvider/index.ts:1 reaches into another package with a relative path (../../../index.js) — import the package by name instead. — core/context/providers/JiraIssuesContextProvider/index.ts:1
core/context/providers/OSContextProvider.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/OSContextProvider.ts:3
core/context/providers/OpenFilesContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/OpenFilesContextProvider.ts:1
core/context/providers/PostgresContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/PostgresContextProvider.ts:1
core/context/providers/ProblemsContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/ProblemsContextProvider.ts:1
core/context/providers/SearchContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/SearchContextProvider.ts:1
core/context/providers/TerminalContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/TerminalContextProvider.ts:1
core/context/providers/URLContextProvider.ts:6 reaches into another package with a relative path (../../index.js) — import the package by name instead. — core/context/providers/URLContextProvider.ts:6
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
provideInlineCompletionItems has cyclomatic complexity 60 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — extensions/vscode/src/autocomplete/completionProvider.ts:150
constructLlmApi has cyclomatic complexity 55 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/openai-adapters/src/index.ts:84
(anonymous) has cyclomatic complexity 44 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — gui/src/redux/thunks/streamNormalInput.ts:81
streamUpdate has cyclomatic complexity 35 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:524
handleResponsesFinal has cyclomatic complexity 34 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/llm/openaiTypeConverters.ts:622
analyzeError has cyclomatic complexity 34 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — gui/src/util/errorAnalysis.ts:38
(anonymous) has cyclomatic complexity 33 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/fetch/src/node-fetch-patch.js:171
convertVercelStreamPart has cyclomatic complexity 32 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/openai-adapters/src/vercelStreamConverter.ts:83
postprocessCompletion has cyclomatic complexity 31 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/autocomplete/postprocessing/index.ts:92
streamChat has cyclomatic complexity 30 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/llm/index.ts:1095
_convertMessages has cyclomatic complexity 29 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/llm/llms/Bedrock.ts:362
(anonymous) has cyclomatic complexity 29 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/llm/llms/OpenAI.ts:62
migrateJsonSharedConfig has cyclomatic complexity 29 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/config/migrateSharedConfig.ts:18
constructor has cyclomatic complexity 29 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/llm/llms/VertexAI.ts:61
fetchwithRequestOptions has cyclomatic complexity 29 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/fetch/src/fetch.ts:82
isCriticalCommand has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:402
searchFiles has cyclomatic complexity 28 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — manual-testing-sandbox/next-edit/next-edit-6-3.ts:232
autodetectTemplateType has cyclomatic complexity 28 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/llm/autodetect.ts:313
defaultShouldRetry has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — core/llm/utils/retry.ts:42
fromResponsesChunk has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/openai-adapters/src/apis/openaiResponses.ts:575
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files7.3 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
REDACTED has 1375 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
core/llm/index.ts has 1351 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/llm/index.ts:1
core/core.ts has 1295 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/core.ts:1
packages/terminal-security/src/evaluateTerminalCommandSecurity.ts has 1110 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:1
core/autocomplete/filtering/streamTransforms/lineStream.vitest.ts has 1099 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/autocomplete/filtering/streamTransforms/lineStream.vitest.ts:1
core/config/types.ts has 1095 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/config/types.ts:1
core/llm/openaiTypeConverters.ts has 1041 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/llm/openaiTypeConverters.ts:1
REDACTED has 1030 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts has 910 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:1
extensions/vscode/src/activation/NextEditWindowManager.ts has 900 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/activation/NextEditWindowManager.ts:1
extensions/vscode/src/commands.ts has 836 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/commands.ts:1
core/config/load.ts has 833 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/config/load.ts:1
extensions/cli/src/ui/UserInput.tsx has 804 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/cli/src/ui/UserInput.tsx:1
extensions/vscode/src/activation/NextEditWindowManager.vitest.ts has 803 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/activation/NextEditWindowManager.vitest.ts:1
core/llm/llms/Cohere.vitest.ts has 801 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/llm/llms/Cohere.vitest.ts:1
core/nextEdit/NextEditEditableRegionCalculator.ts has 784 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/nextEdit/NextEditEditableRegionCalculator.ts:1
core/indexing/CodebaseIndexer.ts has 781 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/indexing/CodebaseIndexer.ts:1
core/autocomplete/context/static-context/StaticContextService.ts has 777 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/autocomplete/context/static-context/StaticContextService.ts:1
extensions/cli/src/ui/hooks/useChat.ts has 774 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/cli/src/ui/hooks/useChat.ts:1
extensions/vscode/src/activation/SelectionChangeManager.vitest.ts has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/activation/SelectionChangeManager.vitest.ts:1
core/llm/llms/Ollama.ts has 752 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/llm/llms/Ollama.ts:1
packages/openai-adapters/src/apis/openaiResponses.ts has 722 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/openai-adapters/src/apis/openaiResponses.ts:1
core/tools/implementations/runTerminalCommand.vitest.ts has 718 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/tools/implementations/runTerminalCommand.vitest.ts:1
core/llm/llms/Bedrock.ts has 691 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/llm/llms/Bedrock.ts:1
packages/openai-adapters/src/apis/Bedrock.ts has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/openai-adapters/src/apis/Bedrock.ts:1
core/llm/llms/OpenAI.ts has 655 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/llm/llms/OpenAI.ts:1
extensions/vscode/src/autocomplete/completionProvider.ts has 633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/autocomplete/completionProvider.ts:1
extensions/vscode/src/VsCodeIde.ts has 617 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/VsCodeIde.ts:1
core/diff/myers.vitest.ts has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/diff/myers.vitest.ts:1
core/autocomplete/filtering/streamTransforms/lineStream.ts has 600 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/autocomplete/filtering/streamTransforms/lineStream.ts:1
extensions/cli/src/stream/streamChatResponse.helpers.ts has 574 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/cli/src/stream/streamChatResponse.helpers.ts:1
core/context/mcp/MCPConnection.ts has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — core/context/mcp/MCPConnection.ts:1
extensions/vscode/src/util/ideUtils.ts has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/util/ideUtils.ts:1
manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts:1
extensions/vscode/src/diff/vertical/handler.ts has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/diff/vertical/handler.ts:1
extensions/cli/src/commands/chat.ts has 564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/cli/src/commands/chat.ts:1
REDACTED has 563 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
gui/src/components/mainInput/AtMentionDropdown/index.tsx has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — gui/src/components/mainInput/AtMentionDropdown/index.tsx:1
gui/src/context/SubmenuContextProviders.tsx has 556 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — gui/src/context/SubmenuContextProviders.tsx:1
extensions/vscode/src/diff/vertical/manager.ts has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — extensions/vscode/src/diff/vertical/manager.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage8.8 / 10Strong✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:1, core/nextEdit/NextEditEditableRegionCalculator.ts:1, manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
What to do
Bump outdated dependencies to current versions to limit upgrade debt.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code6.4 / 10Adequate✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
110 file(s) (~22106 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: extensions/vscode/src/extension.ts imports './.buildTimestamp', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — extensions/vscode
1 file(s) (~55 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — packages/continue-sdk/typescript
Unreachable from the 97 application, 44 tooling and 504 test entry point(s) detected in this repo. Gate removals on `npm run tsc:watch:gui` — an undetected custom entry would make these reachable.
no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×36) — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts, core/nextEdit/NextEditEditableRegionCalculator.ts, manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts, …
no import path from any entry point (97 application, 44 tooling, 504 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docs-site/components/ui/command.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — docs-site/components/ui/dialog.tsx
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×16) — core/indexing/test/indexing.ts:1, core/llm/llms/Asksage.ts:1, core/llm/llms/Ollama.ts:2, …
Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — extensions/vscode/src/autocomplete/lsp.ts:24
Declared in binary/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
core/autocomplete/CompletionProvider.ts → core/autocomplete/util/AutocompleteLoggingService.ts → core/data/log.ts → core/core.ts → core/autocomplete/CompletionProvider.ts (one verified cycle inside a mutually-dependent group of 92 files) — core/autocomplete/CompletionProvider.ts:18
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped6.1 / 10Adequate✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`renderedSVG.svg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — gui/src/components/StyledMarkdownPreview/MermaidBlock.tsx:99
`info` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — gui/src/pages/config/sections/ToolsSection.tsx:397
`name` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — manual-testing-sandbox/next-edit/next-edit-9-5.ts:107
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.
Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. 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.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/1 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.
What to do
Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 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 — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 50 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.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — #1 transferring dockerfile: 3.35kB done #1 DONE 0.0s REDACTED:1 -------------------- 1 | >>> <?xml version="1.0" encoding="UTF-8"?> 2 | <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> 3 | <plist version="1.0"> -------------------- ERROR: failed to solve: dockerfile parse error on line 1: unknown instruction: <?xml; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D12 Dependency Hygiene — Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 5 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Kotlin, PHP, Python, Ruby, Rust, TypeScript, html not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed JavaScript, TypeScript surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .java, .kt, .php, .py, .rb, .rs, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 8 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Aggregate boundaries — 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
DM10 One transaction, one aggregate — 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
DM2 Strongly-typed ids — 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
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
DM4 Rich vs anemic model — 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
DM5 Encapsulated state — 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
DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
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 (this repository commits no MSBuild project, so its C# was read as syntax-only projects — a handler marked ONLY by an interface from a package is not visible without a build)
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
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 measured — the application kind could not be determined for this repo
P8 Schema migrations — Django, SQLAlchemy is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — coverage data present for 330 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — no async method does work a token could cancel
X27 Collection changed while being enumerated — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×30
Click handler on a non-interactive <div> docs-site/components/docs/DocsShell.tsx:369— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/ConversationStarters/ConversationStarterCard.tsx:14— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/OSRContextMenu.tsx:169— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/OSRContextMenu.tsx:180— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/OSRContextMenu.tsx:209— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/PageHeader.tsx:18— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StepContainer/ConversationSummary.tsx:45— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/CollapsibleContainer.tsx:32— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/CollapsibleContainer.tsx:44— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/CopyButton.tsx:16— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/FileInfo.tsx:24— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/InsertButton.tsx:19— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/RunInTerminalButton.tsx:21— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/ToolbarButtonWithTooltip.tsx:19— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/index.tsx:98— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/ToggleDiv.tsx:30— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> REDACTED:317— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/config/FatalErrorNotice.tsx:44— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/config/FatalErrorNotice.tsx:58— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/config/FatalErrorNotice.tsx:68— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/console/Expander.tsx:14— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/gui/Switch.tsx:39— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/mainInput/InlineErrorMessage.tsx:23— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/mainInput/InputToolbar.tsx:79— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> gui/src/components/mainInput/Lump/LumpToolbar/IsApplyingToolbar.tsx:16— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC1 · Text alternatives· <img> without a text alternative · ×8
<img> without a text alternative gui/src/components/SafeImg.tsx:52— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative gui/src/components/loaders/Loader.tsx:31— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative gui/src/components/modelSelection/ModelCard.tsx:135— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative gui/src/components/modelSelection/ModelCard.tsx:239— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative gui/src/components/modelSelection/ModelSelectionListbox.tsx:109— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative gui/src/components/modelSelection/ModelSelectionListbox.tsx:175— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative gui/src/components/modelSelection/ModelSelectionListbox.tsx:220— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative gui/src/pages/gui/ToolCallDiv/ToolCallDisplay.tsx:51— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC2 · Forms & labels· Custom control with no accessible name on <div> · ×7
Custom control with no accessible name on <div> docs-site/components/docs/DocsShell.tsx:369— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/InsertButton.tsx:19— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> gui/src/components/gui/Switch.tsx:39— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> gui/src/components/mainInput/Lump/LumpToolbar/BlockSettingsTopToolbar.tsx:75— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> gui/src/pages/config/components/UserSetting.tsx:177— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> gui/src/pages/config/components/UserSetting.tsx:182— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
Custom control with no accessible name on <div> gui/src/pages/gui/ToolCallDiv/TerminalCollapsibleContainer.tsx:38— This <div> carries a click handler, which makes it a control, but it has no text, aria-label or labelled child (the icon-only case), so assistive tech has no name to announce for it. Note that switching it to <button type="button"> — the right fix for its keyboard operability — does not give it a name either: an icon-only button still needs one. Add visible text or an aria-label.
AC2 · Forms & labels· <input> without a programmatic label · ×7
<input> without a programmatic label gui/src/components/History/index.tsx:152— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label gui/src/components/modelSelection/ModelSelectionListbox.tsx:135— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label gui/src/pages/config/components/UserSetting.tsx:79— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label gui/src/pages/config/components/UserSetting.tsx:165— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label gui/src/pages/config/components/UserSetting.tsx:196— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label gui/src/styles/ThemePage.tsx:134— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label manual-testing-sandbox/AdvancedPage.tsx:41— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×7
Click handler on a non-interactive <span> gui/src/components/ConversationStarters/ConversationStarterCards.tsx:56— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> gui/src/components/OnboardingCard/components/OnboardingLocalTab.tsx:176— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> gui/src/components/OnboardingCard/components/OnboardingProvidersTab.tsx:113— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> gui/src/components/StyledMarkdownPreview/FilenameLink.tsx:36— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> gui/src/components/StyledMarkdownPreview/SymbolLink.tsx:45— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> gui/src/components/mainInput/InlineErrorMessage.tsx:35— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <span> gui/src/components/mainInput/Lump/LumpToolbar/EditToolbar.tsx:23— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Orphaned knowledge extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditWindowManager.kt:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/nextEdit/NextEditEditableRegionCalculator.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge packages/openai-adapters/src/apis/openaiResponses.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge core/nextEdit/context/aggregateEdits.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
AC2 · Forms & labels· <label> that labels no control · ×6
<label> that labels no control gui/src/components/OnboardingCard/components/OnboardingProvidersTab.tsx:69— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control gui/src/forms/AddModelForm.tsx:194— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control gui/src/forms/AddModelForm.tsx:225— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control gui/src/forms/AddModelForm.tsx:239— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control gui/src/forms/AddModelForm.tsx:328— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control gui/src/forms/AddModelForm.tsx:378— This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
D30 · Dependency Vulnerabilities· High vulnerability · ×5
AC2 · Forms & labels· <select> without a programmatic label · ×2
<select> without a programmatic label gui/src/components/OnboardingCard/components/OnboardingCardTabs.tsx:68— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label manual-testing-sandbox/AdvancedPage.tsx:47— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
Unlisted import 'uri-js' core/config/loadLocalAssistants.ts:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'uri-js' extensions/vscode/src/VsCodeIde.ts:7— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Import cycle (4 files) core/autocomplete/CompletionProvider.ts:18— core/autocomplete/CompletionProvider.ts → core/autocomplete/util/AutocompleteLoggingService.ts → core/data/log.ts → core/core.ts → core/autocomplete/CompletionProvider.ts (one verified cycle inside a mutually-dependent group of 92 files)
Import cycle (4 files) core/context/retrieval/pipelines/BaseRetrievalPipeline.ts:19— core/context/retrieval/pipelines/BaseRetrievalPipeline.ts → core/tools/callTool.ts → core/tools/implementations/codebaseTool.ts → core/context/retrieval/retrieval.ts → core/context/retrieval/pipelines/BaseRetrievalPipeline.ts (one verified cycle inside a mutually-dependent group of 6 files)
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text gui/src/components/DeprecationBanner.tsx:46— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC4 · Keyboard semantics· Click handler on a non-interactive <li> · ×1
Click handler on a non-interactive <li> gui/src/components/console/ListItem.tsx:35— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Dependency-rule violation: @continuedev/core (Domain) → @continuedev/openai-adapters (Infrastructure) core/package.json:65— `@continuedev/core` is a Domain project but references `@continuedev/openai-adapters`, a Infrastructure project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
Unlisted import '@jest/globals' core/indexing/test/indexing.ts:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'form-data' core/llm/llms/Asksage.ts:1— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'json-schema' core/llm/llms/Ollama.ts:2— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@opentelemetry/sdk-metrics' extensions/cli/src/telemetry/telemetryService.ts:6— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'openai' extensions/cli/src/compaction.ts:5— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'zod' extensions/cli/src/util/loadMarkdownSkills.ts:7— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'lodash' extensions/vscode/src/util/ideUtils.ts:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'yaml' extensions/vscode/src/commands.ts:20— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'highlight.js' gui/src/components/StyledMarkdownPreview/rehypeHighlightPlugin.ts:3— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'data-uri-to-buffer' packages/fetch/src/node-fetch-patch.js:22— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'fetch-blob' packages/fetch/src/node-fetch-patch.js:24— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'formdata-polyfill' packages/fetch/src/node-fetch-patch.js:32— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@aws-sdk/token-providers' packages/openai-adapters/src/apis/Bedrock.ts:33— Imported but not declared in any reachable package.json — installs work only by hoisting accident.
TodoComment sync/src/sync.rs:56— // TODO: Error handle 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 sync/src/sync/mod.rs:56— // TODO: Error handle 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 sync/src/sync.rs:233— // TODO: You could add_bulk, remove_bulk if this gets slow — 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 sync/src/sync/mod.rs:233— // TODO: You could add_bulk, remove_bulk if this gets slow — 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 sync/src/sync.rs:354— // TODO: Use modified files to speed up calculation — 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 sync/src/sync/mod.rs:354— // TODO: Use modified files to speed up calculation — 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 sync/src/sync/merkle.rs:628— // TODO: If a folder was removed, and another added, but they have the same hash, you should then assume it was renamed — 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 packages/openai-adapters/src/test/vercel-sdk.test.ts:47— // TODO: Vercel AI SDK fullStream usage tokens are unreliable - investigate — 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 packages/openai-adapters/src/apis/Anthropic.ts:109— // TODO support custom tools — 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 packages/openai-adapters/src/apis/Anthropic.ts:261— // TODO support custom tool calls — 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 packages/openai-adapters/src/apis/AnthropicUtils.ts:148— // TODO not supported yet — 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 packages/openai-adapters/src/apis/AnthropicUtils.ts:163— // TODO unsafe cast, may be differences between openai tool schema and anthropic tool schema, — 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 packages/openai-adapters/src/apis/Bedrock.ts:409— // this.config.cacheBehavior?.cacheSystemMessage // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/openai-adapters/src/apis/Bedrock.ts:420— // TODO REASONING — 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 packages/openai-adapters/src/apis/Bedrock.ts:451— // TODO tool calls not supported — 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 packages/openai-adapters/src/apis/Bedrock.ts:509— // TODO reasoning — 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 packages/openai-adapters/src/apis/OpenRouter.ts:11— // TODO: Extract detailed error info from OpenRouter's error.metadata.raw to surface better messages — 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 packages/openai-adapters/src/apis/VertexAI.ts:184— // TODO - support anthropic prompt caching with "anthropic-beta" header — 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 packages/llm-info/src/types.ts:21— // providers: string[]; // TODO: uncomment and deal with the consequences — 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 packages/llm-info/src/types.ts:71— // capabilities: ModelProviderCapability[]; // TODO: uncomment and deal with the consequences — 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 packages/fetch/src/fetch.ts:64— // TODO: For streamed responses, this caused the response to be consumed and the connection would just hang open — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/fetch/src/util.ts:84— // TODO IP address ranges — 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 packages/fetch/src/util.ts:86— // TODO CIDR notation — 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 packages/continue-sdk/python/api/openapi_client/api_client.py:64— # TODO remove as only py3 is supported? — 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 packages/config-yaml/src/schemas/models.ts:35— // TODO consider just using array of strings for model capabilities — 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.
FunctionTooLong: useChat.useChat extensions/cli/src/ui/hooks/useChat.ts:48— FunctionTooLong — useChat runs 511 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 411 over it, 5.11× 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: UserInput.UserInput extensions/cli/src/ui/UserInput.tsx:118— FunctionTooLong — UserInput runs 495 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 395 over it, 4.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.
FunctionTooLong: index.AtMentionDropdown gui/src/components/mainInput/AtMentionDropdown/index.tsx:161— FunctionTooLong — AtMentionDropdown runs 335 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 235 over it, 3.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: serve.serve REDACTED:74— FunctionTooLong — serve runs 313 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 213 over it, 3.13× 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: AddModelForm.AddModelForm gui/src/forms/AddModelForm.tsx:33— FunctionTooLong — AddModelForm runs 302 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 202 over it, 3.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SubmenuContextProviders.SubmenuContextProvidersProvider gui/src/context/SubmenuContextProviders.tsx:139— FunctionTooLong — SubmenuContextProvidersProvider runs 288 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 188 over it, 2.88× 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: ToolsSection.MCPServerPreview gui/src/pages/config/sections/ToolsSection.tsx:61— FunctionTooLong — MCPServerPreview runs 276 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 176 over it, 2.76× 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: load.intermediateToFinalConfig core/config/load.ts:234— FunctionTooLong — intermediateToFinalConfig runs 261 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 161 over it, 2.61× 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: TUIChat.TUIChat extensions/cli/src/ui/TUIChat.tsx:152— FunctionTooLong — TUIChat runs 256 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 156 over it, 2.56× 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: Chat.Chat gui/src/pages/gui/Chat.tsx:106— FunctionTooLong — Chat runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MCPSelector.MCPSelector extensions/cli/src/ui/MCPSelector.tsx:53— FunctionTooLong — MCPSelector runs 250 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 150 over it, 2.50× 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: UserSettingsSection.UserSettingsSection gui/src/pages/config/sections/UserSettingsSection.tsx:14— FunctionTooLong — UserSettingsSection runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× 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: MCPAppRenderer.McpAppRenderer gui/src/pages/gui/ToolCallDiv/MCPAppRenderer.tsx:92— FunctionTooLong — McpAppRenderer runs 233 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 133 over it, 2.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.
FunctionTooLong: editorConfig.createEditorConfig gui/src/components/mainInput/TipTapEditor/utils/editorConfig.ts:79— FunctionTooLong — createEditorConfig runs 219 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 119 over it, 2.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: StreamError.StreamErrorDialog gui/src/pages/gui/StreamError.tsx:26— FunctionTooLong — StreamErrorDialog runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.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: node-fetch-patch.fetch packages/fetch/src/node-fetch-patch.js:71— FunctionTooLong — fetch runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: doLoadConfig.doLoadConfig core/config/profile/doLoadConfig.ts:64— FunctionTooLong — doLoadConfig runs 202 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 102 over it, 2.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.StepContainerPreToolbar gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/index.tsx:43— FunctionTooLong — StepContainerPreToolbar runs 196 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 96 over it, 1.96× 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: FindAndReplace.FindAndReplaceDisplay gui/src/pages/gui/ToolCallDiv/FindAndReplace.tsx:86— FunctionTooLong — FindAndReplaceDisplay runs 195 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 95 over it, 1.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.
FunctionTooLong: EditMessageSelector.EditMessageSelector extensions/cli/src/ui/EditMessageSelector.tsx:19— FunctionTooLong — EditMessageSelector runs 191 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 91 over it, 1.91× 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: TipTapEditor.TipTapEditorInner gui/src/components/mainInput/TipTapEditor/TipTapEditor.tsx:48— FunctionTooLong — TipTapEditorInner runs 186 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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: FindWidget.useFindWidget gui/src/components/find/FindWidget.tsx:58— FunctionTooLong — useFindWidget runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× 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: DocsShell.DocsShell docs-site/components/docs/DocsShell.tsx:206— FunctionTooLong — DocsShell runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× 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: InputToolbar.InputToolbar gui/src/components/mainInput/InputToolbar.tsx:49— FunctionTooLong — InputToolbar runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) 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.
FunctionTooLong: TotalUsage.CostChart gui/src/components/console/TotalUsage.tsx:25— FunctionTooLong — CostChart runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× 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.
+ 46 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×63
Sync-over-async blocking binary/utils/bundle-binary.js:31— `fs.copyFileSync` in `downloadNodeSqlite` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking binary/utils/bundle-binary.js:40— `fs.unlinkSync` in `downloadNodeSqlite` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking binary/utils/bundle-binary.js:48— `fs.mkdirSync` in `bundleForBinary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking binary/utils/bundle-binary.js:56— `fs.copyFileSync` in `bundleForBinary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking binary/utils/bundle-binary.js:68— `fs.writeFileSync` in `bundleForBinary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking binary/utils/ripgrep.js:35— `fs.writeFileSync` in `downloadFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking binary/utils/ripgrep.js:61— `fs.writeFileSync` in `extractArchive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking binary/utils/ripgrep.js:90— `fs.mkdirSync` in `downloadRipgrep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking binary/utils/ripgrep.js:106— `fs.chmodSync` in `downloadRipgrep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/autocomplete/context/root-path-context/test/testUtils.ts:58— `fs.cpSync` in `testRootPathContext` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/autocomplete/context/root-path-context/test/testUtils.ts:66— `fs.readFileSync` in `testRootPathContext` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/config/load.ts:737— `execSync` in `buildConfigTsWithBinary` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/config/load.ts:767— `fs.existsSync` in `buildConfigTsandReadConfigJs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/config/load.ts:771— `fs.readFileSync` in `buildConfigTsandReadConfigJs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/config/profile/doLoadConfig.ts:90— `fs.existsSync` in `doLoadConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/config/profile/doLoadConfig.ts:110— `fs.existsSync` in `doLoadConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:135— `execSync` in `getWorkspaceDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/data/devdataSqlite.ts:77— `fs.existsSync` in `get` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/data/log.ts:95— `fs.writeFileSync` in `logLocalData` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/data/log.ts:223— `fs.existsSync` in `logToOneDestination` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/data/log.ts:224— `fs.mkdirSync` in `logToOneDestination` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/data/log.ts:228— `fs.writeFileSync` in `logToOneDestination` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/indexing/refreshIndex.ts:93— `fs.existsSync` in `get` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/test/jest.global-setup.ts:8— `fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking core/test/jest.global-setup.ts:9— `fs.rmSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Boundary violation [package:relative-cross-package] binary/build.js:6— binary/build.js:6 reaches into another package with a relative path (../scripts/util) — import the package by name instead.
Boundary violation [package:relative-cross-package] binary/build.js:11— binary/build.js:11 reaches into another package with a relative path (../extensions/vscode/scripts/install-copy-nodemodule) — import the package by name instead.
Boundary violation [package:relative-cross-package] binary/utils/bundle-binary.js:8— binary/utils/bundle-binary.js:8 reaches into another package with a relative path (../../scripts/util) — import the package by name instead.
Boundary violation [package:relative-cross-package] binary/utils/bundle-binary.js:14— binary/utils/bundle-binary.js:14 reaches into another package with a relative path (../../extensions/vscode/scripts/download-copy-sqlite) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/autocomplete/CompletionProvider.ts:2— core/autocomplete/CompletionProvider.ts:2 reaches into another package with a relative path (../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/autocomplete/postprocessing/index.ts:4— core/autocomplete/postprocessing/index.ts:4 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/autocomplete/templating/AutocompleteTemplate.ts:3— core/autocomplete/templating/AutocompleteTemplate.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/autocomplete/templating/index.ts:7— core/autocomplete/templating/index.ts:7 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/commands/slash/built-in-legacy/cmd.ts:2— core/commands/slash/built-in-legacy/cmd.ts:2 reaches into another package with a relative path (../../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/commands/slash/built-in-legacy/commit.ts:1— core/commands/slash/built-in-legacy/commit.ts:1 reaches into another package with a relative path (../../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/commands/slash/built-in-legacy/http.ts:2— core/commands/slash/built-in-legacy/http.ts:2 reaches into another package with a relative path (../../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/commands/slash/built-in-legacy/review.ts:1— core/commands/slash/built-in-legacy/review.ts:1 reaches into another package with a relative path (../../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/commands/slash/built-in-legacy/share.ts:4— core/commands/slash/built-in-legacy/share.ts:4 reaches into another package with a relative path (../../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/commands/slash/mcpSlashCommand.ts:3— core/commands/slash/mcpSlashCommand.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/config/ConfigHandler.ts:3— core/config/ConfigHandler.ts:3 reaches into another package with a relative path (../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/config/ProfileLifecycleManager.ts:7— core/config/ProfileLifecycleManager.ts:7 reaches into another package with a relative path (../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/config/profile/IProfileLoader.ts:4— core/config/profile/IProfileLoader.ts:4 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/config/profile/LocalProfileLoader.ts:3— core/config/profile/LocalProfileLoader.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/context/index.ts:1— core/context/index.ts:1 reaches into another package with a relative path (../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/context/providers/CodeContextProvider.ts:1— core/context/providers/CodeContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/context/providers/DatabaseContextProvider.ts:3— core/context/providers/DatabaseContextProvider.ts:3 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/context/providers/DebugLocalsProvider.ts:1— core/context/providers/DebugLocalsProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/context/providers/DiffContextProvider.ts:1— core/context/providers/DiffContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/context/providers/DiscordContextProvider.ts:1— core/context/providers/DiscordContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] core/context/providers/FileTreeContextProvider.ts:1— core/context/providers/FileTreeContextProvider.ts:1 reaches into another package with a relative path (../../index.js) — import the package by name instead.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/nextEdit/NextEditEditableRegionCalculator.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file extensions/vscode/scripts/prepackage.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/codeRenderer/CodeRenderer.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-10-5.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-6-3.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file extensions/vscode/scripts/utils.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-7-4-sol.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file gui/src/components/console/TotalUsage.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-9-5.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file docs-site/lib/docs.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file extensions/vscode/src/terminal/terminalEmulator.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-5-3.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file gui/src/components/modelSelection/ModelCard.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file gui/src/hooks/useLLMLog.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file binary/build.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file manual-testing-sandbox/next-edit/next-edit-4-2-sol.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file extensions/cli/src/hooks/fireHook.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file core/protocol/messenger/messageIde.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Skipped test: CLI tool format tests skipped - no OpenAI API key packages/openai-adapters/src/test/cli-tools.test.ts:131— Skipped — switched off by test.skip
Skipped test: should successfully stream multi-part chat with image packages/openai-adapters/src/test/util.ts:160— Skipped — switched off by test.skip
Skipped test: Tool Call second message works packages/openai-adapters/src/test/util.ts:319— Skipped — switched off by test.skip
Skipped test: OpenAI tests skipped - no API key packages/openai-adapters/src/test/vercel-sdk.test.ts:74— Skipped — switched off by test.skip
Skipped test: Anthropic tests skipped - no API key packages/openai-adapters/src/test/vercel-sdk.test.ts:97— Skipped — switched off by test.skip
Skipped test: OpenAI comparison tests skipped - no API key packages/openai-adapters/src/test/vercel-sdk.test.ts:104— Skipped — switched off by test.skip
Skipped test: Anthropic comparison tests skipped - no API key packages/openai-adapters/src/test/vercel-sdk.test.ts:268— Skipped — switched off by test.skip
Skipped test: should make a real API call to the Continue service packages/continue-sdk/typescript/tests/continue.test.ts:13— Skipped — switched off by test.skip
Skipped test: should prioritize org over user / package secrets packages/config-yaml/src/__tests__/index.test.ts:412— Skipped — switched off by it.skip
Skipped test: should display correct panel description extensions/vscode/e2e/tests/GUI.test.ts:53— Skipped — switched off by it.skip
Skipped test: should display tutorial card after accepting onboarding quick start extensions/vscode/e2e/tests/GUI.test.ts:62— Skipped — switched off by it.skip
Skipped test: Should create a code block with the whole file when Cmd+L is pressed on an empty line extensions/vscode/e2e/tests/KeyboardShortcuts.test.ts:223— Skipped — switched off by it.skip
Skipped test: Should create a code block when Cmd+L is pressed on a non-empty line extensions/vscode/e2e/tests/KeyboardShortcuts.test.ts:243— Skipped — switched off by it.skip
Skipped test: should detect when new files are created extensions/cli/src/util/fileWatcher.test.ts:30— Skipped — switched off by it.skip
Skipped test: should detect when files are deleted extensions/cli/src/util/fileWatcher.test.ts:45— Skipped — switched off by it.skip
Skipped test: should handle SIGINT (Ctrl+C) by exiting process extensions/cli/src/util/prompt.test.ts:102— Skipped — switched off by it.skip
Skipped test: should output response and exit with -p flag extensions/cli/src/e2e/headless-simple.test.ts:32— Skipped — switched off by it.skip
Skipped test: should handle streaming responses in headless mode extensions/cli/src/e2e/headless-simple.test.ts:37— Skipped — switched off by it.skip
Skipped test: should work with minimal config extensions/cli/src/e2e/headless-simple.test.ts:57— Skipped — switched off by it.skip
Skipped test: should have /exit endpoint that returns success response extensions/cli/src/commands/serve.test.ts:88— Skipped — switched off by it.skip
Skipped test: should handle a string with CRLF line endings core/util/index.test.ts:276— Skipped — switched off by it.skip
Skipped test: should handle strings with tabs core/util/index.test.ts:284— Skipped — switched off by it.skip
Skipped test: returns correct intersection for single line overlap core/util/ranges.test.ts:305— Skipped — switched off by test.skip
Skipped test: should only re-index the changed files when changing branches core/indexing/CodebaseIndexer.test.ts:257— Skipped — switched off by test.skip
Skipped test: shouldn't re-index anything when changing back to original branch core/indexing/CodebaseIndexer.test.ts:270— Skipped — switched off by test.skip
No assertions: Skipping API key tests packages/openai-adapters/src/test/main.test.ts:202— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Can reject and apply changes from sidebar extensions/vscode/e2e/tests/Apply.test.skip.ts:62— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Should display completions extensions/vscode/e2e/tests/Autocomplete.test.ts:30— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Can submit message by pressing enter extensions/vscode/e2e/tests/GUI.test.ts:106— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Can submit message by button click extensions/vscode/e2e/tests/GUI.test.ts:116— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Can delete messages extensions/vscode/e2e/tests/GUI.test.ts:126— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Can edit messages extensions/vscode/e2e/tests/GUI.test.ts:179— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should successfully use the terminal context provider extensions/vscode/e2e/tests/GUI.test.ts:349— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should repeat back the system message extensions/vscode/e2e/tests/GUI.test.ts:370— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: chat → history → chat extensions/vscode/e2e/tests/GUI.test.ts:531— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Should correctly undo and redo using keyboard shortcuts when writing a chat message extensions/vscode/e2e/tests/KeyboardShortcuts.test.ts:75— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Skipping SSH tests extensions/vscode/e2e/tests/SSH.skip.ts:16— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Should display completions extensions/vscode/e2e/tests/SSH.skip.ts:22— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should handle empty string config path extensions/cli/src/onboarding.test.ts:103— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: works in local mode extensions/cli/src/ui/__tests__/TUIChat.dualModeHelper.tsx:40— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: works in remote mode extensions/cli/src/ui/__tests__/TUIChat.dualModeHelper.tsx:59— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: works in ${mode} mode extensions/cli/src/ui/__tests__/TUIChat.dualModeHelper.tsx:101— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: (unnamed test) extensions/cli/src/ui/__tests__/TUIChat.testHelper.ts:67— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: (unnamed test) extensions/cli/src/ui/__tests__/TUIChat.testHelper.ts:228— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should handle verbose mode initialization extensions/cli/src/services/ResourceMonitoringService.test.ts:93— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: Skipping API key tests core/llm/llm.test.ts:206— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should detect Anthropic models correctly core/llm/llms/OpenRouter.vitest.ts:7— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: should create git repo for testing core/indexing/CodebaseIndexer.test.ts:251— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
FileTooLong: REDACTED REDACTED— FileTooLong — 1109 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: providers (56-1393). The bar is 500 significant lines; this is 609 over it, 2.22× 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: llm/index.ts core/llm/index.ts— FileTooLong — 1055 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: BaseLLM (90-1504). The bar is 500 significant lines; this is 555 over it, 2.11× 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: core/core.ts core/core.ts— FileTooLong — 943 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: Core (89-1460). The bar is 500 significant lines; this is 443 over it, 1.89× 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: docs/DocsService.ts core/indexing/docs/DocsService.ts— FileTooLong — 831 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: DocsService (167-1292). The bar is 500 significant lines; this is 331 over it, 1.66× 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: llm/openaiTypeConverters.ts core/llm/openaiTypeConverters.ts— FileTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 291 over it, 1.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 733 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: sessionSlice (248-1014). The bar is 500 significant lines; this is 233 over it, 1.47× 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/evaluateTerminalCommandSecurity.ts packages/terminal-security/src/evaluateTerminalCommandSecurity.ts— FileTooLong — 688 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 188 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: config/load.ts core/config/load.ts— FileTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 142 over it, 1.28× 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/commands.ts extensions/vscode/src/commands.ts— FileTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded), about 78% of them inside a single declaration: getCommandsMap (108-828). The bar is 500 significant lines; this is 109 over it, 1.22× 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: ui/UserInput.tsx extensions/cli/src/ui/UserInput.tsx— FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: UserInput (118-911). The bar is 500 significant lines; this is 96 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: static-context/StaticContextService.ts core/autocomplete/context/static-context/StaticContextService.ts— FileTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 80 over it, 1.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: activation/NextEditWindowManager.ts extensions/vscode/src/activation/NextEditWindowManager.ts— FileTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: NextEditWindowManager (106-1015). The bar is 500 significant lines; this is 79 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: indexing/CodebaseIndexer.ts core/indexing/CodebaseIndexer.ts— FileTooLong — 571 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: CodebaseIndexer (48-872). The bar is 500 significant lines; this is 71 over it, 1.14× 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: load/unroll.ts packages/config-yaml/src/load/unroll.ts— FileTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 62 over it, 1.12× 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: llms/Ollama.ts core/llm/llms/Ollama.ts— FileTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded), about 79% of them inside a single declaration: Ollama (152-831). The bar is 500 significant lines; this is 55 over it, 1.11× 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: hooks/useChat.ts extensions/cli/src/ui/hooks/useChat.ts— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: useChat (48-881). The bar is 500 significant lines; this is 53 over it, 1.11× 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: apis/openaiResponses.ts packages/openai-adapters/src/apis/openaiResponses.ts— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 53 over it, 1.11× 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: nextEdit/NextEditWindowManager.kt extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditWindowManager.kt— FileTooLong — 548 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 48 over it, 1.10× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: editor/InlineEditPanel.kt extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/editor/InlineEditPanel.kt— FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1 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.
Change coupling: builtIn.ts ↔ index.ts core/tools/builtIn.ts:1— `core/tools/builtIn.ts` and `core/tools/index.ts` change together 78% of the time (14 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 14 shared commits counted here, the most recent 3 are `b6eddec2` add read skill tool; `e9641b00` chore: remove unused search and replace tool (#7487); `c596f8b8` fix: :bug: Remove head tool and move range tool to experimental — run `git show` on any of them.
Change coupling: passThrough.ts ↔ MessageTypes.kt core/protocol/passThrough.ts:1— `core/protocol/passThrough.ts` and `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/constants/MessageTypes.kt` change together 71% of the time (25 of the 35 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 25 shared commits counted here, the most recent 3 are `bcd29eb0` feat: unified dynamic model fetching for all providers; `970552b4` provision to delete rule file; `acbba9b7` fix: :bug: Fixes based on reviewer comments — run `git show` on any of them.
Change coupling: TUIChat.tsx ↔ useChat.types.ts extensions/cli/src/ui/TUIChat.tsx:1— `extensions/cli/src/ui/TUIChat.tsx` and `extensions/cli/src/ui/hooks/useChat.types.ts` change together 71% of the time (10 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `b1557026` feat(cli): export and import sessions (#11075); `dd9177fe` add quiz prompt component; `c7d6a73d` show separate screen for background jobs — run `git show` on any of them.
Change coupling: core.ts ↔ passThrough.ts core/protocol/core.ts:1— `core/protocol/core.ts` and `core/protocol/passThrough.ts` change together 65% of the time (30 of the 46 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 30 shared commits counted here, the most recent 3 are `bcd29eb0` feat: unified dynamic model fetching for all providers; `970552b4` provision to delete rule file; `d192e61a` feat: rehaul onboarding for updated billing (#7965) — run `git show` on any of them.
Change coupling: createRuleBlock.ts ↔ createRuleBlock.ts core/tools/definitions/createRuleBlock.ts:1— `core/tools/definitions/createRuleBlock.ts` and `core/tools/implementations/createRuleBlock.ts` change together 65% of the time (11 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 11 shared commits counted here, the most recent 3 are `fd94ef2b` feat: move rule type logic into `config-yaml`; `7f541da7` improv: naming; `c1467f5e` fix: types — run `git show` on any of them.
Change coupling: core.ts ↔ MessageTypes.kt core/protocol/core.ts:1— `core/protocol/core.ts` and `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/constants/MessageTypes.kt` change together 63% of the time (22 of the 35 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 22 shared commits counted here, the most recent 3 are `bcd29eb0` feat: unified dynamic model fetching for all providers; `970552b4` provision to delete rule file; `d227a571` fix: instant apply for search and replace - vs code and jetbrains — run `git show` on any of them.
Change coupling: findAndReplaceUtils.ts ↔ multiEditImpl.ts core/edit/searchAndReplace/findAndReplaceUtils.ts:1— `core/edit/searchAndReplace/findAndReplaceUtils.ts` and `gui/src/util/clientTools/multiEditImpl.ts` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `6d7bfb96` feat: search and replace fallback reintroduction cont.; `b28ce709` feat: refactor multiedit; `604ec09e` WIP: perform search and replace with fallbacks — run `git show` on any of them.
Change coupling: AddToChatAction.kt ↔ useMainEditorWebviewListeners.ts extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/actions/AddToChatAction.kt:1— `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/actions/AddToChatAction.kt` and `gui/src/components/mainInput/TipTapEditor/useMainEditorWebviewListeners.ts` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f5bee4f5` fix: unify the namings; `8e1288ec` review: fix (at that commit the file was still `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/actions/menu/file/AddToEditAction.kt`); `cbc7ada3` feat: add MentionRepoMapInChatAction.kt (at that commit the file was still `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/actions/menu/file/MentionFilesOrFoldersInChatAction.kt`) — run `git show` on any of them.
Change coupling: ideWebview.ts ↔ AddToChatAction.kt core/protocol/ideWebview.ts:1— `core/protocol/ideWebview.ts` and `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/actions/AddToChatAction.kt` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f5bee4f5` fix: unify the namings; `8e1288ec` review: fix (at that commit the file was still `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/actions/menu/file/AddToEditAction.kt`); `cbc7ada3` feat: add MentionRepoMapInChatAction.kt (at that commit the file was still `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/actions/menu/file/MentionFilesOrFoldersInChatAction.kt`) — run `git show` on any of them.
Change coupling: hubLoader.ts ↔ types.ts extensions/cli/src/hubLoader.ts:1— `extensions/cli/src/hubLoader.ts` and `extensions/cli/src/services/types.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `21624468` feat: full secrets parsing for all CLI flags; `0ecef51a` fix: agent-file -> agentFile; `e6ee11b9` fix: tests, lint, workflow model name logic — run `git show` on any of them.
Change coupling: jest.config.js ↔ vitest.config.ts core/jest.config.js:1— `core/jest.config.js` and `core/vitest.config.ts` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `03017ef1` test only .vitest.ts files; `b6f71438` migrate `context` foler; `1bcb9b21` migrate core config tests to vitest — run `git show` on any of them.
Change coupling: aggregateEdits.ts ↔ REDACTED core/nextEdit/context/aggregateEdits.ts:1— `core/nextEdit/context/aggregateEdits.ts` and `REDACTED` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `a2e01a31` fix latest user diff tracking; `7aebea0e` refactoring and commenting to address patrick's comments; `ef53d113` dev data schemas, edit logging refinement — run `git show` on any of them.
Change coupling: SimpleToolCallUI.tsx ↔ ToolCallDisplay.tsx gui/src/pages/gui/ToolCallDiv/SimpleToolCallUI.tsx:1— `gui/src/pages/gui/ToolCallDiv/SimpleToolCallUI.tsx` and `gui/src/pages/gui/ToolCallDiv/ToolCallDisplay.tsx` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `e583bfde` fix: GUI polish (#7927); `4ad874dc` remove args and tool truncation buttons; `40cb8025` fix: revert showing error UI — run `git show` on any of them.
Change coupling: ScreenContent.tsx ↔ useChat.ts extensions/cli/src/ui/components/ScreenContent.tsx:1— `extensions/cli/src/ui/components/ScreenContent.tsx` and `extensions/cli/src/ui/hooks/useChat.ts` change together 50% of the time (11 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 11 shared commits counted here, the most recent 3 are `b1557026` feat(cli): export and import sessions (#11075); `dd9177fe` add quiz prompt component; `c7d6a73d` show separate screen for background jobs — run `git show` on any of them.
Change coupling: ideWebview.ts ↔ editState.ts core/protocol/ideWebview.ts:1— `core/protocol/ideWebview.ts` and `gui/src/redux/slices/editState.ts` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `49d65f69` chore: revert `ApplyState` name (at that commit the file was still `gui/src/redux/slices/editModeState.ts`); `e5072fcd` feat [jb]: pull out apply logic into new class (at that commit the file was still `gui/src/redux/slices/editModeState.ts`); `c6535256` edit mode cleanup (at that commit the file was still `gui/src/redux/slices/editModeState.ts`) — run `git show` on any of them.
Change coupling: editorConfig.ts ↔ editState.ts gui/src/components/mainInput/TipTapEditor/utils/editorConfig.ts:1— `gui/src/components/mainInput/TipTapEditor/utils/editorConfig.ts` and `gui/src/redux/slices/editState.ts` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `c6535256` edit mode cleanup (at that commit the file was still `gui/src/redux/slices/editModeState.ts`); `dfc57bef` progress on apply states (at that commit the file was still `gui/src/redux/slices/editModeState.ts`); `654842a9` working edit apply state (at that commit the file was still `gui/src/redux/slices/editModeState.ts`) — run `git show` on any of them.
Change coupling: ModelSelect.tsx ↔ configSlice.ts gui/src/components/modelSelection/ModelSelect.tsx:1— `gui/src/components/modelSelection/ModelSelect.tsx` and `gui/src/redux/slices/configSlice.ts` 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, and counted over this repository's 10,000 most recent commits rather than its whole history — 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 `55f5ed58` fix: use loading state for loading indicator, better error messages; `0d476473` feat: v1 onboarding card; `7f8882ee` feat: remove `models` property — run `git show` on any of them.
MethodTooLong: Core.registerMessageHandlers core/core.ts:275— MethodTooLong — registerMessageHandlers runs 544 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 444 over it, 5.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ContinueCompletionProvider.provideInlineCompletionItems extensions/vscode/src/autocomplete/completionProvider.ts:150— MethodTooLong — provideInlineCompletionItems runs 284 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 184 over it, 2.84× 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: VsCodeExtension.constructor REDACTED:172— MethodTooLong — constructor runs 260 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 160 over it, 2.60× 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: IdeProtocolClient.handleMessage extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/IdeProtocolClient.kt:52— MethodTooLong — handleMessage runs 253 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 153 over it, 2.53× 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: VsCodeMessenger.constructor extensions/vscode/src/extension/VsCodeMessenger.ts:72— MethodTooLong — constructor runs 215 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 115 over it, 2.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DocsService.indexAndAdd core/indexing/docs/DocsService.ts:435— MethodTooLong — indexAndAdd runs 199 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× 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: MCPConnection.connectClient core/context/mcp/MCPConnection.ts:122— MethodTooLong — connectClient runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× 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: VerticalDiffManager.streamEdit extensions/vscode/src/diff/vertical/manager.ts:357— MethodTooLong — streamEdit runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CompletionProvider.provideInlineCompletionItems core/autocomplete/CompletionProvider.ts:150— MethodTooLong — provideInlineCompletionItems runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DFSWalker.walk core/indexing/walkDir.ts:82— MethodTooLong — walk runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LanceDbIndex.update core/indexing/LanceDbIndex.ts:254— MethodTooLong — update runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: InlineEditPanelKt.openInlineEdit extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/editor/InlineEditPanel.kt:138— MethodTooLong — openInlineEdit runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Anthropic.handleResponse core/llm/llms/Anthropic.ts:265— MethodTooLong — handleResponse runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: providers REDACTED:1— ClassTooLong — 1066 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 666 over it, 2.67× 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: BaseLLM core/llm/index.ts:90— ClassTooLong — 977 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 577 over it, 2.44× 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: Core core/core.ts:89— ClassTooLong — 860 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 460 over it, 2.15× 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: CodebaseIndexer core/indexing/CodebaseIndexer.ts:48— ClassTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 133 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: sessionSlice REDACTED:1— ClassTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 125 over it, 1.31× 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: useChat extensions/cli/src/ui/hooks/useChat.ts:1— ClassTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 111 over it, 1.28× 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: UserInput extensions/cli/src/ui/UserInput.tsx:1— ClassTooLong — 495 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 95 over it, 1.24× 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: Ollama core/llm/llms/Ollama.ts:152— ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 39 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Bedrock core/llm/llms/Bedrock.ts:42— ClassTooLong — 439 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 39 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: IntelliJIDE extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/IntelliJIde.kt:42— ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 28 over it, 1.07× 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: VsCodeIde extensions/vscode/src/VsCodeIde.ts:38— ClassTooLong — 424 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 24 over it, 1.06× 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: VsCodeIde extensions/vscode/src/VsCodeIde.ts:38— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: IntelliJIDE extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/IntelliJIde.kt:42— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. Most of these members implement continueintellijextension.IDE (44 of 48 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: MessageIde core/protocol/messenger/messageIde.ts:21— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: FileSystemIde core/util/filesystem.ts:22— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DocsService core/indexing/docs/DocsService.ts:167— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BaseLLM core/llm/index.ts:90— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TextBuffer extensions/cli/src/ui/TextBuffer.ts:9— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: VsCodeIdeUtils extensions/vscode/src/util/ideUtils.ts:27— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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.
Focus outline removed inline gui/src/components/History/index.tsx:152— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline gui/src/components/OnboardingCard/components/OnboardingCardTabs.tsx:68— <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/ApplyActions.tsx:70— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/CreateFileButton.tsx:14— <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline gui/src/components/modelSelection/ModelSelectionListbox.tsx:135— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline gui/src/styles/ThemePage.tsx:134— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Off the main sequence: @continuedev/fetch — @continuedev/fetch: 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: @continuedev/llm-info — @continuedev/llm-info: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @continuedev/terminal-security — @continuedev/terminal-security: 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: @continuedev/openai-adapters — @continuedev/openai-adapters: abstractness 0.03, instability 0.00, distance 0.97 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @continuedev/config-yaml — @continuedev/config-yaml: abstractness 0.16, instability 0.00, distance 0.84 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
UserInput.UserInput::selectFile (cognitive 24) extensions/cli/src/ui/UserInput.tsx:397— UserInput.UserInput::selectFile has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, error handling 1 (3 pts), 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. This shape REPEATS in the file: 3 other methods here (UserInput.UserInput::updateFileSearchState, UserInput.UserInput::handleSlashCommandNavigation, UserInput.UserInput::renderInputText) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
UserInput.UserInput::handleSlashCommandNavigation (cognitive 19) extensions/cli/src/ui/UserInput.tsx:454— UserInput.UserInput::handleSlashCommandNavigation has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5 (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. This shape REPEATS in the file: 3 other methods here (UserInput.UserInput::updateFileSearchState, UserInput.UserInput::selectFile, UserInput.UserInput::renderInputText) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
UserInput.UserInput::updateFileSearchState (cognitive 17) extensions/cli/src/ui/UserInput.tsx:302— UserInput.UserInput::updateFileSearchState has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (UserInput.UserInput::selectFile, UserInput.UserInput::handleSlashCommandNavigation, UserInput.UserInput::renderInputText) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
UserInput.UserInput::renderInputText (cognitive 16) extensions/cli/src/ui/UserInput.tsx:784— UserInput.UserInput::renderInputText has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: 3 other methods here (UserInput.UserInput::updateFileSearchState, UserInput.UserInput::selectFile, UserInput.UserInput::handleSlashCommandNavigation) have the same decision points, in the same order, at the same nesting depths — so this is one pattern written 4 times rather than 4 independent problems. Splitting this body alone leaves the other 3 exactly as they are. Where these are variations on one operation, the change that clears all 4 is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
Low cohesion: VsCodeIde (LCOM4 18) extensions/vscode/src/VsCodeIde.ts:38— VsCodeIde's methods fall into 18 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 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: VsCodeIdeUtils (LCOM4 10) extensions/vscode/src/util/ideUtils.ts:27— VsCodeIdeUtils's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ChatHistoryService (LCOM4 4) extensions/cli/src/services/ChatHistoryService.ts:23— ChatHistoryService'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.
Low cohesion: UserManagementApp (LCOM4 4) manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts:473— UserManagementApp'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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×3
Focus outline removed in CSS without a :focus replacement gui/src/index.css:53— `*:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement gui/src/components/StyledMarkdownPreview/markdown.css:570— `.wmde-markdown .anchor:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement gui/src/components/mainInput/AtMentionDropdown/index.tsx:129— `textarea:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×3
Animation without a prefers-reduced-motion guard gui/src/components/AnimatedEllipsis.tsx:19— `span::after` moves (`animation: ____________________ 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard gui/src/components/loaders/BlinkingDot.tsx:16— `.css-in-js` moves (`animation: ________ 3s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard REDACTED:22— `span::after` moves (`animation: ______________ 1s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
FixmeComment extensions/intellij/src/test/kotlin/com/github/continuedev/continueintellijextension/unit/UriUtilsTest.kt:14— // fixme it's not working — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/editor/InlineEditPanel.kt:50— // fixme: blocking code on EDT (however this is not a regression compared to the latest changes) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment core/indexing/CodebaseIndexer.ts:246— // FIXME: by returning here, there is a chance that while paused a file is modified and — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (40 lines × 2 locations) core/llm/llms/Asksage.ts:262— core/llm/llms/Asksage.ts:262 · core/llm/llms/Asksage.ts:338 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (40 lines × 2 locations) extensions/cli/src/tools/edit.ts:148— extensions/cli/src/tools/edit.ts:148 · extensions/cli/src/tools/multiEdit.ts:137 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (40 lines × 2 locations) extensions/cli/src/ui/hooks/useChat.ts:540— extensions/cli/src/ui/hooks/useChat.ts:540 · extensions/cli/src/ui/hooks/useChat.ts:607 — 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.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×3
Untrusted text written into markup unescaped gui/src/components/StyledMarkdownPreview/MermaidBlock.tsx:99— `renderedSVG.svg` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped gui/src/pages/config/sections/ToolsSection.tsx:397— `info` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped manual-testing-sandbox/next-edit/next-edit-9-5.ts:107— `name` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
AC3 · Page structure· Page without a main landmark · ×2
Page without a main landmark docs-site/app/layout.tsx:20— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark manual-testing-sandbox/test.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
LlamaTokenizer.encode (cyclomatic 18) REDACTED:243— LlamaTokenizer.encode has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
LlamaTokenizer.encode (cyclomatic 18) REDACTED:243— LlamaTokenizer.encode has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
gemini-types.convertJsonSchemaToGeminiSchema (cyclomatic 18) core/llm/llms/gemini-types.ts:68— gemini-types.convertJsonSchemaToGeminiSchema 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.
gemini-types.convertJsonSchemaToGeminiSchema (cyclomatic 18) packages/openai-adapters/src/util/gemini-types.ts:68— gemini-types.convertJsonSchemaToGeminiSchema 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.
encode (cognitive 27) REDACTED:243— encode has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 3, boolean chains 2 (nesting depth added 8). Of this number, 26 points are the body's own statements and 1 belongs to 2 function items inside it that branch. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
encode (cognitive 27) REDACTED:243— encode has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (22 pts), loops 3, boolean chains 2 (nesting depth added 8). Of this number, 26 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
gemini-types.convertJsonSchemaToGeminiSchema (cognitive 21) core/llm/llms/gemini-types.ts:68— gemini-types.convertJsonSchemaToGeminiSchema has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
gemini-types.convertJsonSchemaToGeminiSchema (cognitive 21) packages/openai-adapters/src/util/gemini-types.ts:68— gemini-types.convertJsonSchemaToGeminiSchema has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (17 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
Duplicated block (9 lines × 2) extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/GitService.kt:59— extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/GitService.kt:59-67 | extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/IntelliJIde.kt:727-735 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) extensions/intellij/src/main/resources/continue_tutorial.java:27— extensions/intellij/src/main/resources/continue_tutorial.java:27-35 | extensions/intellij/src/main/resources/continue_tutorial.java:46-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 `extensions/intellij/src/main/resources/continue_tutorial.java:27` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (18 lines × 2) extensions/intellij/src/main/resources/continue_tutorial.py:26— extensions/intellij/src/main/resources/continue_tutorial.py:26-43 | extensions/vscode/continue_tutorial.py:26-43 — before extracting anything, compare `extensions/intellij/src/main/resources/continue_tutorial.py` and `extensions/vscode/continue_tutorial.py` as WHOLE FILES: 92% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) sync/src/lib.rs:74— sync/src/lib.rs:74-91 | sync/src/lib.rs:112-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (39 lines × 2 locations) gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx:5— gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx:5 · gui/src/pages/config/sections/HelpSection.tsx:21 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (39 lines × 2 locations) gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx:68— gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx:68 · gui/src/pages/config/sections/HelpSection.tsx:84 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
Duplicated block (37 lines × 2 locations) extensions/cli/src/ui/EditMessageSelector.tsx:189— extensions/cli/src/ui/EditMessageSelector.tsx:189 · extensions/cli/src/ui/UserInput.tsx:808 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (37 lines × 2 locations) gui/src/components/modelSelection/ModelSelectionListbox.tsx:158— gui/src/components/modelSelection/ModelSelectionListbox.tsx:158 · gui/src/components/modelSelection/ModelSelectionListbox.tsx:203 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (31 lines × 2 locations) REDACTED:207— REDACTED:207 · REDACTED:242 — 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 (31 lines × 2 locations) gui/src/pages/stats.tsx:70— gui/src/pages/stats.tsx:70 · gui/src/pages/stats.tsx:102 — 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.
R10 · Code Duplication· Duplicated block with local edits (30 matched lines × 2 locations) · ×2
Duplicated block with local edits (30 matched lines × 2 locations) core/indexing/LanceDbIndex.ts:500— core/indexing/LanceDbIndex.ts:500 · core/indexing/chunk/ChunkCodebaseIndex.ts:206 — the two spans are one implementation copied and then locally edited — 185 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (30 matched lines × 2 locations) core/llm/llms/OpenAI.ts:655— core/llm/llms/OpenAI.ts:655 · core/llm/llms/SiliconFlow.ts:23 — the two spans are one implementation copied and then locally edited — 162 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Dead file (~91 LoC) gui/src/pages/config/components/ConfigItemSelect.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~91 LoC) manual-testing-sandbox/next-edit/next-edit-test-2.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC3 · Page structure· Data table has no header cells · ×1
Data table has no header cells gui/src/components/History/index.tsx:188— A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
AC4 · Keyboard semantics· Link used as a button (placeholder href) · ×1
Link used as a button (placeholder href) REDACTED:521— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
Positive tabindex (1) gui/src/components/console/List.tsx:33— A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 247 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
Core.registerMessageHandlers (cyclomatic 70) core/core.ts:275— Core.registerMessageHandlers has cyclomatic complexity 70 (threshold 15). Most of this is not in the body itself: 1 of the 70 points is its own statement and the rest belongs to 31 function items inside it that branch (a function literal at line 907, refreshIfNotIgnored, a function literal at line 944, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ContinueCompletionProvider.provideInlineCompletionItems (cyclomatic 61) extensions/vscode/src/autocomplete/completionProvider.ts:150— ContinueCompletionProvider.provideInlineCompletionItems has cyclomatic complexity 61 (threshold 15). Of this number, 59 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MCPSelector.MCPSelector (cyclomatic 59) extensions/cli/src/ui/MCPSelector.tsx:53— MCPSelector.MCPSelector has cyclomatic complexity 59 (threshold 15). Most of this is not in the body itself: 7 of the 59 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 226, getServerInfoDisplay, handleServerAction, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
fetch (cyclomatic 59) packages/fetch/src/node-fetch-patch.js:71— fetch has cyclomatic complexity 59 (threshold 15). Most of this is not in the body itself: 1 of the 59 points is its own statement and the rest belongs to 19 function items inside it that branch (a function literal at line 171, a function literal at line 72, (anonymous)::abort, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
runTerminalCommand.runTerminalCommandImpl (cyclomatic 56) core/tools/implementations/runTerminalCommand.ts:109— runTerminalCommand.runTerminalCommandImpl has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 10 of the 56 points are its own statements and the rest belongs to 16 function literals inside it that branch (lines 276, 125, 205, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.constructLlmApi (cyclomatic 55) packages/openai-adapters/src/index.ts:84— index.constructLlmApi has cyclomatic complexity 55 (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.
evaluateTerminalCommandSecurity.isCriticalCommand (cyclomatic 53) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:402— evaluateTerminalCommandSecurity.isCriticalCommand has cyclomatic complexity 53 (threshold 15). Of this number, 34 points are the body's own statements and 19 belong to 5 function literals inside it that branch. 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.
IdeProtocolClient.handleMessage (cyclomatic 52) extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/IdeProtocolClient.kt:52— IdeProtocolClient.handleMessage has cyclomatic complexity 52 (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.
SubmenuContextProviders.SubmenuContextProvidersProvider (cyclomatic 51) gui/src/context/SubmenuContextProviders.tsx:139— SubmenuContextProviders.SubmenuContextProvidersProvider has cyclomatic complexity 51 (threshold 15). Most of this is not in the body itself: 1 of the 51 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 317, 471, 225, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
serve.serve (cyclomatic 47) REDACTED:74— serve.serve has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 14 of the 47 points are its own statements and the rest belongs to 15 function items inside it that branch (processMessages, a function literal at line 251, a function literal at line 228, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.AtMentionDropdown (cyclomatic 46) gui/src/components/mainInput/AtMentionDropdown/index.tsx:161— index.AtMentionDropdown has cyclomatic complexity 46 (threshold 15). Most of this is not in the body itself: 5 of the 46 points are its own statements and the rest belongs to 13 function items inside it that branch (selectItem, a function literal at line 416, a function literal at line 535, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
streamNormalInput.streamNormalInput (cyclomatic 45) gui/src/redux/thunks/streamNormalInput.ts:81— streamNormalInput.streamNormalInput has cyclomatic complexity 45 (threshold 15). Of this number, 44 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MCPConnection.connectClient (cyclomatic 44) core/context/mcp/MCPConnection.ts:122— MCPConnection.connectClient has cyclomatic complexity 44 (threshold 15). Most of this is not in the body itself: 13 of the 44 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 215, 201, 172). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AddModelForm.AddModelForm (cyclomatic 44) gui/src/forms/AddModelForm.tsx:33— AddModelForm.AddModelForm has cyclomatic complexity 44 (threshold 15). Of this number, 27 points are the body's own statements and 17 belong to 12 function items inside it that branch. 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.
QuizPrompt.QuizPrompt (cyclomatic 43) extensions/cli/src/ui/components/QuizPrompt.tsx:19— QuizPrompt.QuizPrompt has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 12 of the 43 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 36, 80, 117, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FindAndReplace.FindAndReplaceDisplay (cyclomatic 42) gui/src/pages/gui/ToolCallDiv/FindAndReplace.tsx:86— FindAndReplace.FindAndReplaceDisplay has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 8 of the 42 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 288, renderContainer, a function literal at line 128, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TaskManager.searchTasks (cyclomatic 42) manual-testing-sandbox/next-edit/next-edit-10-5.ts:332— TaskManager.searchTasks has cyclomatic complexity 42 (threshold 15). Most of this is not in the body itself: 5 of the 42 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 336, 402). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
EditMessageSelector.EditMessageSelector (cyclomatic 41) extensions/cli/src/ui/EditMessageSelector.tsx:19— EditMessageSelector.EditMessageSelector has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 5 of the 41 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 122, a function literal at line 80, renderEditText, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TipTapEditor.TipTapEditorInner (cyclomatic 41) gui/src/components/mainInput/TipTapEditor/TipTapEditor.tsx:48— TipTapEditor.TipTapEditorInner has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 9 of the 41 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 124, 152, 131, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MCPAppRenderer.McpAppRenderer (cyclomatic 38) gui/src/pages/gui/ToolCallDiv/MCPAppRenderer.tsx:92— MCPAppRenderer.McpAppRenderer has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 8 of the 38 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 277, 303, 314, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Chat.Chat (cyclomatic 38) gui/src/pages/gui/Chat.tsx:106— Chat.Chat has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 11 of the 38 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 267, 161, 138, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
unroll.unrollBlocks (cyclomatic 37) packages/config-yaml/src/load/unroll.ts:367— unroll.unrollBlocks has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 13 of the 37 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 411, 497, 545, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GeminiApi._convertBody (cyclomatic 37) packages/openai-adapters/src/apis/Gemini.ts:115— GeminiApi._convertBody has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 12 of the 37 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 149, 165, 137, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.StepContainerPreToolbar (cyclomatic 36) gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/index.tsx:43— index.StepContainerPreToolbar has cyclomatic complexity 36 (threshold 15). Of this number, 17 points are the body's own statements and 19 belong to 9 function items inside it that branch. 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.
load.intermediateToFinalConfig (cyclomatic 35) core/config/load.ts:234— load.intermediateToFinalConfig has cyclomatic complexity 35 (threshold 15). Of this number, 16 points are the body's own statements and 19 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
openaiTypeConverters.handleResponsesFinal (cyclomatic 34) core/llm/openaiTypeConverters.ts:622— openaiTypeConverters.handleResponsesFinal has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DocsService.indexAndAdd (cyclomatic 34) core/indexing/docs/DocsService.ts:435— DocsService.indexAndAdd has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolsSection.MCPServerPreview (cyclomatic 32) gui/src/pages/config/sections/ToolsSection.tsx:61— ToolsSection.MCPServerPreview has cyclomatic complexity 32 (threshold 15). Of this number, 21 points are the body's own statements and 11 belong to 7 function items inside it that branch. 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.
index.postprocessCompletion (cyclomatic 31) core/autocomplete/postprocessing/index.ts:92— index.postprocessCompletion has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Bedrock._convertMessages (cyclomatic 31) core/llm/llms/Bedrock.ts:362— Bedrock._convertMessages has cyclomatic complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NextEditEditableRegionCalculator.staticRerankJump (cyclomatic 31) core/nextEdit/NextEditEditableRegionCalculator.ts:247— NextEditEditableRegionCalculator.staticRerankJump has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 belong to 2 function literals inside it that branch. 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.
JobsSelector.JobsSelector (cyclomatic 31) extensions/cli/src/ui/JobsSelector.tsx:29— JobsSelector.JobsSelector has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 8 of the 31 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 51, 37, 180, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
errorAnalysis.analyzeError (cyclomatic 31) gui/src/util/errorAnalysis.ts:38— errorAnalysis.analyzeError has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
validation.validateConfig (cyclomatic 30) core/config/validation.ts:10— validation.validateConfig has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 20, validateTabAutocompleteModel, a function literal at line 87, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
loadYaml.configYamlToContinueConfig (cyclomatic 30) core/config/yaml/loadYaml.ts:156— loadYaml.configYamlToContinueConfig has cyclomatic complexity 30 (threshold 15). Of this number, 19 points are the body's own statements and 11 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BaseLLM.streamChat (cyclomatic 29) core/llm/index.ts:1095— BaseLLM.streamChat has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
migrateSharedConfig.migrateJsonSharedConfig (cyclomatic 29) core/config/migrateSharedConfig.ts:18— migrateSharedConfig.migrateJsonSharedConfig has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InputToolbar.InputToolbar (cyclomatic 29) gui/src/components/mainInput/InputToolbar.tsx:49— InputToolbar.InputToolbar has cyclomatic complexity 29 (threshold 15). Of this number, 22 points are the body's own statements and 7 belong to 3 function literals inside it that branch. 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.
OSRContextMenu.OSRContextMenu (cyclomatic 29) gui/src/components/OSRContextMenu.tsx:13— OSRContextMenu.OSRContextMenu has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 50, a function literal at line 43, onMenuItemClick). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
OpenAI.formatMessageForO1OrGpt5ForResponses (cyclomatic 28) core/llm/llms/OpenAI.ts:60— OpenAI.formatMessageForO1OrGpt5ForResponses has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
autodetect.autodetectTemplateType (cyclomatic 28) core/llm/autodetect.ts:313— autodetect.autodetectTemplateType has cyclomatic complexity 28 (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.
SessionSelector.SessionSelector (cyclomatic 28) extensions/cli/src/ui/SessionSelector.tsx:39— SessionSelector.SessionSelector has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 94, 145, 49, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
next-edit-6-3.searchFiles (cyclomatic 28) manual-testing-sandbox/next-edit/next-edit-6-3.ts:232— next-edit-6-3.searchFiles 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.
fetch.fetchwithRequestOptions (cyclomatic 28) packages/fetch/src/fetch.ts:82— fetch.fetchwithRequestOptions has cyclomatic complexity 28 (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.
vercelStreamConverter.convertVercelStreamPart (cyclomatic 28) packages/openai-adapters/src/vercelStreamConverter.ts:83— vercelStreamConverter.convertVercelStreamPart has cyclomatic complexity 28 (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.
BedrockApi._convertMessages (cyclomatic 28) packages/openai-adapters/src/apis/Bedrock.ts:170— BedrockApi._convertMessages has cyclomatic complexity 28 (threshold 15). Of this number, 25 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
evaluateTerminalCommandSecurity.isSafeCommand (cyclomatic 28) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:979— evaluateTerminalCommandSecurity.isSafeCommand has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
openaiTypeConverters.toResponsesInput (cyclomatic 27) core/llm/openaiTypeConverters.ts:986— openaiTypeConverters.toResponsesInput has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
doLoadConfig.doLoadConfig (cyclomatic 27) core/config/profile/doLoadConfig.ts:64— doLoadConfig.doLoadConfig has cyclomatic complexity 27 (threshold 15). Of this number, 19 points are the body's own statements and 8 belong to 6 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useChat.useChat (cyclomatic 27) extensions/cli/src/ui/hooks/useChat.ts:48— useChat.useChat has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 77, 269, 175, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
VsCodeExtension.constructor (cyclomatic 27) REDACTED:172— VsCodeExtension.constructor has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 13 function items inside it that branch (getUsingFullFileDiff, a function literal at line 218, a function literal at line 564, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
refreshIndex.getAddRemoveForTag (cyclomatic 26) core/indexing/refreshIndex.ts:138— refreshIndex.getAddRemoveForTag has cyclomatic complexity 26 (threshold 15). Of this number, 18 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
VertexAI.constructor (cyclomatic 26) core/llm/llms/VertexAI.ts:61— VertexAI.constructor has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
retry.defaultShouldRetry (cyclomatic 26) core/llm/utils/retry.ts:42— retry.defaultShouldRetry has cyclomatic complexity 26 (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.
OpenRouterCaching.applyAnthropicCachingToOpenRouterBody (cyclomatic 26) packages/openai-adapters/src/apis/OpenRouterCaching.ts:154— OpenRouterCaching.applyAnthropicCachingToOpenRouterBody has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 4 of the 26 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 225, 172, 203, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Gemini.prepareBody (cyclomatic 25) core/llm/llms/Gemini.ts:234— Gemini.prepareBody has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 6 of the 25 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 257, 291, 241, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AutocompleteTemplate.getTemplateForModel (cyclomatic 25) core/autocomplete/templating/AutocompleteTemplate.ts:517— AutocompleteTemplate.getTemplateForModel has cyclomatic complexity 25 (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.
Selector.Selector (cyclomatic 25) extensions/cli/src/ui/Selector.tsx:30— Selector.Selector has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 3 of the 25 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 53, a function literal at line 44, defaultRenderOption, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ServiceDebugger.ServiceDebugger (cyclomatic 25) extensions/cli/src/ui/ServiceDebugger.tsx:29— ServiceDebugger.ServiceDebugger has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 10 of the 25 points are its own statements and the rest belongs to 3 function items inside it that branch (getServiceDetails, getServiceStatus, a function literal at line 85). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
constructMessages.constructMessages (cyclomatic 25) gui/src/redux/util/constructMessages.ts:37— constructMessages.constructMessages has cyclomatic complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
InMemoryTaskRepository.matchesSearchCriteria (cyclomatic 25) manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:296— InMemoryTaskRepository.matchesSearchCriteria has cyclomatic complexity 25 (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.
openaiResponses.fromResponsesChunk (cyclomatic 25) packages/openai-adapters/src/apis/openaiResponses.ts:575— openaiResponses.fromResponsesChunk 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.
sharedConfig.modifyAnyConfigWithSharedConfig (cyclomatic 24) core/config/sharedConfig.ts:91— sharedConfig.modifyAnyConfigWithSharedConfig has cyclomatic complexity 24 (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.
diffFormatting.extractMetadataFromUnifiedDiff (cyclomatic 24) core/nextEdit/context/diffFormatting.ts:138— diffFormatting.extractMetadataFromUnifiedDiff 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.
VerticalDiffManager.streamEdit (cyclomatic 24) extensions/vscode/src/diff/vertical/manager.ts:357— VerticalDiffManager.streamEdit has cyclomatic complexity 24 (threshold 15). Of this number, 18 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
remarkTables.remarkTables (cyclomatic 24) gui/src/components/StyledMarkdownPreview/utils/remarkTables.tsx:23— remarkTables.remarkTables has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 25, 140, 83, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ToolPolicyItem.ToolPolicyItem (cyclomatic 24) gui/src/pages/config/components/ToolPolicyItem.tsx:29— ToolPolicyItem.ToolPolicyItem has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to 3 function literals inside it that branch. 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.
evaluateTerminalCommandSecurity.isHighRiskCommand (cyclomatic 24) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:942— evaluateTerminalCommandSecurity.isHighRiskCommand has cyclomatic complexity 24 (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.
DFSWalker.walk (cyclomatic 23) core/indexing/walkDir.ts:82— DFSWalker.walk has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
filterCodeBlock.filterCodeBlockLines (cyclomatic 23) core/autocomplete/filtering/streamTransforms/filterCodeBlock.ts:31— filterCodeBlock.filterCodeBlockLines has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
parseSystemToolCall.handleToolCallBuffer (cyclomatic 23) core/tools/systemMessageTools/toolCodeblocks/parseSystemToolCall.ts:11— parseSystemToolCall.handleToolCallBuffer has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolPermissionSelector.ToolPermissionSelector (cyclomatic 23) extensions/cli/src/ui/components/ToolPermissionSelector.tsx:57— ToolPermissionSelector.ToolPermissionSelector has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 3 of the 23 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 74, 145). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SyntaxHighlighter.highlightCode (cyclomatic 23) extensions/cli/src/ui/SyntaxHighlighter.ts:82— SyntaxHighlighter.highlightCode has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (processNode, getTextContent). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
StreamError.StreamErrorDialog (cyclomatic 23) gui/src/pages/gui/StreamError.tsx:26— StreamError.StreamErrorDialog has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
UnifiedTerminal.UnifiedTerminalCommand (cyclomatic 23) REDACTED:338— UnifiedTerminal.UnifiedTerminalCommand has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 3 function items inside it that branch. 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.
TaskManager.updateTask (cyclomatic 23) manual-testing-sandbox/next-edit/next-edit-10-5.ts:186— TaskManager.updateTask has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Anthropic.handleResponse (cyclomatic 22) core/llm/llms/Anthropic.ts:265— Anthropic.handleResponse has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hookRunner.aggregateResults (cyclomatic 22) extensions/cli/src/hooks/hookRunner.ts:333— hookRunner.aggregateResults has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MemoizedMessage.MemoizedMessage (cyclomatic 22) extensions/cli/src/ui/components/MemoizedMessage.tsx:51— MemoizedMessage.MemoizedMessage has cyclomatic complexity 22 (threshold 15). Of this number, 13 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
getTheme.getTheme (cyclomatic 22) extensions/vscode/src/util/getTheme.ts:56— getTheme.getTheme has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LumpToolbar.LumpToolbar (cyclomatic 22) gui/src/components/mainInput/Lump/LumpToolbar/LumpToolbar.tsx:49— LumpToolbar.LumpToolbar has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 10 of the 22 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 129, handleStopAction, a function literal at line 124, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
renderSlashCommand.renderSlashCommandPrompt (cyclomatic 22) gui/src/components/mainInput/TipTapEditor/utils/renderSlashCommand.ts:13— renderSlashCommand.renderSlashCommandPrompt has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FileStorageManager.matchesQuery (cyclomatic 22) manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts:402— FileStorageManager.matchesQuery has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
openaiToVercelMessages.convertOpenAIMessagesToVercel (cyclomatic 22) packages/openai-adapters/src/openaiToVercelMessages.ts:24— openaiToVercelMessages.convertOpenAIMessagesToVercel has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AnthropicCachingStrategies.optimizedStrategy (cyclomatic 22) packages/openai-adapters/src/apis/AnthropicCachingStrategies.ts:87— AnthropicCachingStrategies.optimizedStrategy has cyclomatic complexity 22 (threshold 15). Of this number, 14 points are the body's own statements and 8 belong to 4 function literals inside it that branch. 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.
autodetect.autodetectPromptTemplates (cyclomatic 21) core/llm/autodetect.ts:471— autodetect.autodetectPromptTemplates has cyclomatic complexity 21 (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.
useChat.helpers.processSlashCommandResult (cyclomatic 21) extensions/cli/src/ui/hooks/useChat.helpers.ts:58— useChat.helpers.processSlashCommandResult has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TUIChat.TUIChat (cyclomatic 21) extensions/cli/src/ui/TUIChat.tsx:152— TUIChat.TUIChat has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
errorHandling.handleLLMError (cyclomatic 21) extensions/vscode/src/util/errorHandling.ts:9— errorHandling.handleLLMError has cyclomatic complexity 21 (threshold 15). Of this number, 15 points are the body's own statements and 6 belong to 2 function literals inside it that branch. 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.
ModelSelectionListbox.ModelSelectionListbox (cyclomatic 21) gui/src/components/modelSelection/ModelSelectionListbox.tsx:54— ModelSelectionListbox.ModelSelectionListbox has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 belong to 6 function literals inside it that branch. 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.
StepContainer.StepContainer (cyclomatic 21) REDACTED:21— StepContainer.StepContainer has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to one function literal inside it that branches. 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.
ParallelListeners.ParallelListeners (cyclomatic 21) gui/src/hooks/ParallelListeners.tsx:37— ParallelListeners.ParallelListeners has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 56, 106, 127, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DocsIndexingStatus.DocsIndexingStatus (cyclomatic 21) gui/src/pages/config/sections/docs/DocsIndexingStatus.tsx:28— DocsIndexingStatus.DocsIndexingStatus has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 belong to 7 function items inside it that branch. 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.
BracketMatchingService.stopOnUnmatchedClosingBracket (cyclomatic 20) core/autocomplete/filtering/BracketMatchingService.ts:41— BracketMatchingService.stopOnUnmatchedClosingBracket 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.
openaiTypeConverters.convertThinkingMessageToReasoningItem (cyclomatic 20) core/llm/openaiTypeConverters.ts:845— openaiTypeConverters.convertThinkingMessageToReasoningItem has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GitLabMergeRequestContextProvider.getContextItems (cyclomatic 20) REDACTED:145— GitLabMergeRequestContextProvider.getContextItems has cyclomatic complexity 20 (threshold 15). Of this number, 13 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CompletionProvider.provideInlineCompletionItems (cyclomatic 20) core/autocomplete/CompletionProvider.ts:150— CompletionProvider.provideInlineCompletionItems has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useUserInput.handleControlKeys (cyclomatic 20) extensions/cli/src/ui/hooks/useUserInput.ts:23— useUserInput.handleControlKeys has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useChat.imageProcessing.detectImageFormat (cyclomatic 20) extensions/cli/src/ui/hooks/useChat.imageProcessing.ts:60— useChat.imageProcessing.detectImageFormat has cyclomatic complexity 20 (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.
ToolResultSummary.ToolResultSummary (cyclomatic 20) extensions/cli/src/ui/ToolResultSummary.tsx:18— ToolResultSummary.ToolResultSummary 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 shape REPEATS in the file: one other method here (ToolResultSummary.ToolResultSummary::getSummary) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
editorConfig.createEditorConfig (cyclomatic 20) gui/src/components/mainInput/TipTapEditor/utils/editorConfig.ts:79— editorConfig.createEditorConfig has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 9 of the 20 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 306, 288, 327, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
openaiTypeConverters.appendReasoningFieldsIfSupported (cyclomatic 19) core/llm/openaiTypeConverters.ts:45— openaiTypeConverters.appendReasoningFieldsIfSupported 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.
Bedrock._streamChat (cyclomatic 19) core/llm/llms/Bedrock.ts:107— Bedrock._streamChat has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Gemini.processGeminiResponse (cyclomatic 19) core/llm/llms/Gemini.ts:370— Gemini.processGeminiResponse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OpenRouter.modifyChatBody (cyclomatic 19) core/llm/llms/OpenRouter.ts:111— OpenRouter.modifyChatBody has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to 4 function literals inside it that branch. 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.
callTool.callToolFromUri (cyclomatic 19) core/tools/callTool.ts:67— callTool.callToolFromUri has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
interceptSystemToolCalls.interceptSystemToolCalls (cyclomatic 19) core/tools/systemMessageTools/interceptSystemToolCalls.ts:24— interceptSystemToolCalls.interceptSystemToolCalls has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
systemMessage.constructSystemMessage (cyclomatic 19) extensions/cli/src/systemMessage.ts:161— systemMessage.constructSystemMessage has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
handleToolCalls.handleToolCalls (cyclomatic 19) extensions/cli/src/stream/handleToolCalls.ts:36— handleToolCalls.handleToolCalls has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UserInput.UserInput::handleEscapeKey (cyclomatic 19) extensions/cli/src/ui/UserInput.tsx:623— UserInput.UserInput::handleEscapeKey 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.
ToolResultSummary.ToolResultSummary::getSummary (cyclomatic 19) extensions/cli/src/ui/ToolResultSummary.tsx:170— ToolResultSummary.ToolResultSummary::getSummary has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ToolResultSummary.ToolResultSummary) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
NextEditWindowManager.setupListeners (cyclomatic 19) extensions/vscode/src/activation/NextEditWindowManager.ts:603— NextEditWindowManager.setupListeners has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 606, 666, 648, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ExpandableToolbarPreview.ExpandableToolbarPreview (cyclomatic 19) gui/src/components/mainInput/TipTapEditor/components/ExpandableToolbarPreview.tsx:96— ExpandableToolbarPreview.ExpandableToolbarPreview has cyclomatic complexity 19 (threshold 15). Of this number, 12 points are the body's own statements and 7 belong to 5 function literals inside it that branch. 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.
markdown.markdownChunker (cyclomatic 18) core/indexing/chunk/markdown.ts:61— markdown.markdownChunker 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.
NextEditEditableRegionCalculator.doesRangePartiallyOverlap (cyclomatic 18) core/nextEdit/NextEditEditableRegionCalculator.ts:869— NextEditEditableRegionCalculator.doesRangePartiallyOverlap has cyclomatic complexity 18 (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.
chat.runHeadlessMode (cyclomatic 18) extensions/cli/src/commands/chat.ts:436— chat.runHeadlessMode 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.
findWidgetSearch.searchWithinContainer (cyclomatic 18) gui/src/components/find/findWidgetSearch.ts:20— findWidgetSearch.searchWithinContainer has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 45, 70, 134). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FindWidget.useFindWidget (cyclomatic 18) gui/src/components/find/FindWidget.tsx:58— FindWidget.useFindWidget has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 6 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 115, 191, 201). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ContinueInputBox.ContinueInputBox (cyclomatic 18) gui/src/components/mainInput/ContinueInputBox.tsx:55— ContinueInputBox.ContinueInputBox has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 4 function literals inside it that branch. 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.
resolveEditorContent.gatherContextItems (cyclomatic 18) gui/src/components/mainInput/TipTapEditor/utils/resolveEditorContent.ts:111— resolveEditorContent.gatherContextItems has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
UserSetting.UserSetting (cyclomatic 18) gui/src/pages/config/components/UserSetting.tsx:61— UserSetting.UserSetting has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (renderControl, a function literal at line 99, a function literal at line 87). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ModelCard.ModelCard (cyclomatic 18) gui/src/components/modelSelection/ModelCard.tsx:89— ModelCard.ModelCard has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong to 3 function literals inside it that branch. 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.
util.customFetch::letRequestOptionsOverrideAuthHeaders (cyclomatic 18) packages/openai-adapters/src/util.ts:162— util.customFetch::letRequestOptionsOverrideAuthHeaders 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.
VertexAIApi.setupAuthentication (cyclomatic 18) packages/openai-adapters/src/apis/VertexAI.ts:72— VertexAIApi.setupAuthentication 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.
Gemini.removeSystemMessage (cyclomatic 17) core/llm/llms/Gemini.ts:101— Gemini.removeSystemMessage 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.
Ollama._streamChat::convertChatMessage (cyclomatic 17) core/llm/llms/Ollama.ts:539— Ollama._streamChat::convertChatMessage 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.
streamDiff.streamDiff (cyclomatic 17) core/diff/streamDiff.ts:14— streamDiff.streamDiff has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
streamChat.llmStreamChat (cyclomatic 17) core/llm/streamChat.ts:9— streamChat.llmStreamChat 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.
formatError.formatError (cyclomatic 17) extensions/cli/src/util/formatError.ts:4— formatError.formatError 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.
executor.executeSubAgent (cyclomatic 17) extensions/cli/src/subagent/executor.ts:58— executor.executeSubAgent has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
streamChatResponse.processStreamingResponse (cyclomatic 17) extensions/cli/src/stream/streamChatResponse.ts:197— streamChatResponse.processStreamingResponse 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.
index.StyledMarkdownPreview (cyclomatic 17) gui/src/components/StyledMarkdownPreview/index.tsx:188— index.StyledMarkdownPreview has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 240, 333, 292, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ModelSelect.ModelSelect (cyclomatic 17) gui/src/components/modelSelection/ModelSelect.tsx:120— ModelSelect.ModelSelect has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
IndexingProgress.IndexingProgress (cyclomatic 17) gui/src/pages/config/features/indexing/IndexingProgress.tsx:25— IndexingProgress.IndexingProgress has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (onClick, onClickRetry, a function literal at line 42, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RulesSection.RuleCard (cyclomatic 17) gui/src/pages/config/sections/RulesSection.tsx:135— RulesSection.RuleCard has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 4 function items inside it that branch. 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.
useLLMSummary.useLLMSummary (cyclomatic 17) gui/src/hooks/useLLMSummary.ts:12— useLLMSummary.useLLMSummary has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 13). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
validation.validateConfigYaml (cyclomatic 17) packages/config-yaml/src/validation.ts:21— validation.validateConfigYaml has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 37). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
openaiResponses.collectAssistantContentParts (cyclomatic 17) packages/openai-adapters/src/apis/openaiResponses.ts:157— openaiResponses.collectAssistantContentParts 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.
openaiResponses.toResponsesInput (cyclomatic 17) packages/openai-adapters/src/apis/openaiResponses.ts:287— openaiResponses.toResponsesInput has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
util.addModel (cyclomatic 16) core/config/util.ts:26— util.addModel has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 31, 59, 61, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
tree-sitter-utils.extractTopLevelDeclsWithFormatting (cyclomatic 16) core/autocomplete/context/static-context/tree-sitter-utils.ts:81— tree-sitter-utils.extractTopLevelDeclsWithFormatting 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.
LanceDbIndex.update (cyclomatic 16) core/indexing/LanceDbIndex.ts:254— LanceDbIndex.update has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CodebaseIndexer.refreshDirs (cyclomatic 16) core/indexing/CodebaseIndexer.ts:334— CodebaseIndexer.refreshDirs 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.
Cohere._streamChat (cyclomatic 16) core/llm/llms/Cohere.ts:155— Cohere._streamChat 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.
WatsonX._streamChat (cyclomatic 16) core/llm/llms/WatsonX.ts:265— WatsonX._streamChat 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.
loadJsonMcpConfigs.loadJsonMcpConfigs (cyclomatic 16) core/context/mcp/json/loadJsonMcpConfigs.ts:27— loadJsonMcpConfigs.loadJsonMcpConfigs has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
findSearchMatch.findFuzzyMatch (cyclomatic 16) core/edit/searchAndReplace/findSearchMatch.ts:224— findSearchMatch.findFuzzyMatch 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.
CodeRenderer.convertShikiHtmlToSvgGut (cyclomatic 16) core/codeRenderer/CodeRenderer.ts:270— CodeRenderer.convertShikiHtmlToSvgGut has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function literals inside it that branch (lines 325, 285, 308, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
LLMLogFormatter.logMessage (cyclomatic 16) core/llm/logFormatter.ts:286— LLMLogFormatter.logMessage 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.
NextEditEditableRegionCalculator.compareAsts::traverse (cyclomatic 16) core/nextEdit/NextEditEditableRegionCalculator.ts:710— NextEditEditableRegionCalculator.compareAsts::traverse has cyclomatic complexity 16 (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.
CodeGroup.CodeGroup (cyclomatic 16) docs-site/components/docs/mdx/CodeGroup.tsx:11— CodeGroup.CodeGroup has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 14). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
systemMessage.loadMarkdownRulesWithMetadata (cyclomatic 16) extensions/cli/src/systemMessage.ts:89— systemMessage.loadMarkdownRulesWithMetadata 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.
index.initializeServices (cyclomatic 16) extensions/cli/src/services/index.ts:62— index.initializeServices has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
metadata.calculateDiffStats (cyclomatic 16) extensions/cli/src/util/metadata.ts:27— metadata.calculateDiffStats has cyclomatic complexity 16 (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.
review.review (cyclomatic 16) extensions/cli/src/commands/review.ts:261— review.review has cyclomatic complexity 16 (threshold 15). Of this number, 11 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MarkdownRenderer.MarkdownRenderer (cyclomatic 16) extensions/cli/src/ui/MarkdownRenderer.tsx:22— MarkdownRenderer.MarkdownRenderer has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 5 function items inside it that branch (renderMarkdown, a function literal at line 127, a function literal at line 184, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
expandSnippet.expandSnippet (cyclomatic 16) extensions/vscode/src/util/expandSnippet.ts:12— expandSnippet.expandSnippet has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
session.saveCurrentSession (cyclomatic 16) gui/src/redux/thunks/session.ts:192— session.saveCurrentSession 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.
useMainEditorWebviewListeners.useMainEditorWebviewListeners (cyclomatic 16) gui/src/components/mainInput/TipTapEditor/useMainEditorWebviewListeners.ts:17— useMainEditorWebviewListeners.useMainEditorWebviewListeners has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 113, 194, 204, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ModeSelect.ModeSelect (cyclomatic 16) gui/src/components/ModeSelect/ModeSelect.tsx:19— ModeSelect.ModeSelect has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to 4 function literals inside it that branch. 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.
editOutcomeLogger.extractPromptAndCompletion (cyclomatic 16) gui/src/util/editOutcomeLogger.ts:55— editOutcomeLogger.extractPromptAndCompletion has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AskSageApi.chatCompletionStream (cyclomatic 16) packages/openai-adapters/src/apis/AskSage.ts:376— AskSageApi.chatCompletionStream has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
evaluateTerminalCommandSecurity.evaluateTokens (cyclomatic 16) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:176— evaluateTerminalCommandSecurity.evaluateTokens 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.
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: GitDiffCache refreshes cache after expiration core/autocomplete/snippets/gitDiffCache.vitest.ts:22— This test starts work it did not wait for (`cache`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 200))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
TodoComment repeated across 10 files packages/llm-info/src/types.ts:16— The identical TodoComment appears in 10 files (39 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 39 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
HackComment gui/src/components/find/findWidgetSearch.ts:71— // Hacky way to detect code blocks that be wider than client and cause absolute positioning to fail — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
runTerminalCommand.runTerminalCommandImpl (cognitive 152) core/tools/implementations/runTerminalCommand.ts:109— runTerminalCommand.runTerminalCommandImpl has cognitive complexity 152 (threshold 15). Drivers by points: if/else 40 (122 pts), error handling 3 (11 pts), boolean chains 10, ternaries 2 (9 pts) (nesting depth added 97). Of this number, 22 points are the body's own statements and 130 belong to 16 function literals inside it that branch. 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.
ContinueCompletionProvider.provideInlineCompletionItems (cognitive 90) extensions/vscode/src/autocomplete/completionProvider.ts:150— ContinueCompletionProvider.provideInlineCompletionItems has cognitive complexity 90 (threshold 15). Drivers by points: if/else 45 (71 pts), boolean chains 14, loops 2 (5 pts) (nesting depth added 29). Of this number, 89 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Core.registerMessageHandlers (cognitive 89) core/core.ts:275— Core.registerMessageHandlers has cognitive complexity 89 (threshold 15). Drivers by points: if/else 47 (59 pts), error handling 8 (10 pts), boolean chains 7, ternaries 5 (7 pts), loops 3 (6 pts) (nesting depth added 19). None of this is in the body itself: all 89 points belong to 31 function items inside it that branch (a function literal at line 907, a function literal at line 944, refreshIfNotIgnored, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
openaiTypeConverters.handleResponsesFinal (cognitive 86) core/llm/openaiTypeConverters.ts:622— openaiTypeConverters.handleResponsesFinal has cognitive complexity 86 (threshold 15). Drivers by points: if/else 15 (49 pts), ternaries 4 (16 pts), loops 3 (12 pts), boolean chains 9 (nesting depth added 55). 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.
fetch (cognitive 82) packages/fetch/src/node-fetch-patch.js:71— fetch has cognitive complexity 82 (threshold 15). Drivers by points: if/else 33 (57 pts), boolean chains 13, loops 1 (4 pts), error handling 2 (3 pts), ternaries 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 30). None of this is in the body itself: all 82 points belong to 19 function items inside it that branch (a function literal at line 171, a function literal at line 72, (anonymous)::abort, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Bedrock._convertMessages (cognitive 79) core/llm/llms/Bedrock.ts:362— Bedrock._convertMessages has cognitive complexity 79 (threshold 15). Drivers by points: if/else 23 (58 pts), ternaries 2 (8 pts), boolean chains 7, loops 2 (6 pts) (nesting depth added 45). Of this number, 76 points are the body's own statements and 3 belong to one function item inside it that branches. 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.
BedrockApi._convertMessages (cognitive 75) packages/openai-adapters/src/apis/Bedrock.ts:170— BedrockApi._convertMessages has cognitive complexity 75 (threshold 15). Drivers by points: if/else 22 (58 pts), ternaries 2 (8 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 45). Of this number, 66 points are the body's own statements and 9 belong to 2 function items inside it that branch. 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.
DFSWalker.walk (cognitive 71) core/indexing/walkDir.ts:82— DFSWalker.walk has cognitive complexity 71 (threshold 15). Drivers by points: if/else 19 (51 pts), ternaries 3 (12 pts), loops 3 (6 pts), boolean chains 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.
SubmenuContextProviders.SubmenuContextProvidersProvider (cognitive 70) gui/src/context/SubmenuContextProviders.tsx:139— SubmenuContextProviders.SubmenuContextProvidersProvider has cognitive complexity 70 (threshold 15). Drivers by points: if/else 39 (55 pts), boolean chains 6, ternaries 3 (5 pts), error handling 2, loops 2 (nesting depth added 18). None of this is in the body itself: all 70 points belong to 9 function literals inside it that branch (lines 317, 471, 225, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.AtMentionDropdown (cognitive 69) gui/src/components/mainInput/AtMentionDropdown/index.tsx:161— index.AtMentionDropdown has cognitive complexity 69 (threshold 15). Drivers by points: if/else 29 (39 pts), ternaries 10 (22 pts), boolean chains 8 (nesting depth added 22). Most of this is not in the body itself: 5 of the 69 points are its own statements and the rest belongs to 13 function items inside it that branch (selectItem, a function literal at line 416, a function literal at line 535, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
load.intermediateToFinalConfig (cognitive 67) core/config/load.ts:234— load.intermediateToFinalConfig has cognitive complexity 67 (threshold 15). Drivers by points: if/else 37 (53 pts), error handling 2 (6 pts), ternaries 4 (5 pts), loops 2, boolean chains 1 (nesting depth added 21). Of this number, 23 points are the body's own statements and 44 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
interceptSystemToolCalls.interceptSystemToolCalls (cognitive 64) core/tools/systemMessageTools/interceptSystemToolCalls.ts:24— interceptSystemToolCalls.interceptSystemToolCalls has cognitive complexity 64 (threshold 15). Drivers by points: if/else 13 (53 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 45). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
unroll.unrollBlocks (cognitive 64) packages/config-yaml/src/load/unroll.ts:367— unroll.unrollBlocks has cognitive complexity 64 (threshold 15). Drivers by points: if/else 22 (37 pts), loops 6 (8 pts), error handling 3 (7 pts), ternaries 4 (7 pts), boolean chains 5 (nesting depth added 24). Of this number, 16 points are the body's own statements and 48 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
streamNormalInput.streamNormalInput (cognitive 63) gui/src/redux/thunks/streamNormalInput.ts:81— streamNormalInput.streamNormalInput has cognitive complexity 63 (threshold 15). Drivers by points: if/else 24 (34 pts), boolean chains 13, loops 5 (10 pts), error handling 2 (3 pts), ternaries 3 (nesting depth added 16). Of this number, 62 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MCPSelector.MCPSelector (cognitive 61) extensions/cli/src/ui/MCPSelector.tsx:53— MCPSelector.MCPSelector has cognitive complexity 61 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 12, ternaries 6 (10 pts), match/switch 4 (5 pts), error handling 2 (3 pts) (nesting depth added 16). Most of this is not in the body itself: 4 of the 61 points are its own statements and the rest belongs to 12 function items inside it that branch (a function literal at line 226, a function literal at line 85, getServerInfoDisplay, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
OpenAI.formatMessageForO1OrGpt5ForResponses (cognitive 59) core/llm/llms/OpenAI.ts:60— OpenAI.formatMessageForO1OrGpt5ForResponses has cognitive complexity 59 (threshold 15). Drivers by points: if/else 15 (40 pts), loops 3 (9 pts), ternaries 3 (8 pts), match/switch 1 (2 pts) (nesting depth added 37). Of this number, 58 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parseSystemToolCall.handleToolCallBuffer (cognitive 57) core/tools/systemMessageTools/toolCodeblocks/parseSystemToolCall.ts:11— parseSystemToolCall.handleToolCallBuffer has cognitive complexity 57 (threshold 15). Drivers by points: if/else 18 (45 pts), error handling 1 (5 pts), ternaries 1 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 34). 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.
BaseLLM.streamChat (cognitive 56) core/llm/index.ts:1095— BaseLLM.streamChat has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (41 pts), loops 4 (10 pts), boolean chains 2, ternaries 2, error handling 1 (nesting depth added 28). 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.
GeminiApi._convertBody (cognitive 56) packages/openai-adapters/src/apis/Gemini.ts:115— GeminiApi._convertBody has cognitive complexity 56 (threshold 15). Drivers by points: if/else 18 (30 pts), ternaries 6 (11 pts), boolean chains 10, error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 20). Most of this is not in the body itself: 14 of the 56 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 149, 165, 137, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
loadYaml.configYamlToContinueConfig (cognitive 55) core/config/yaml/loadYaml.ts:156— loadYaml.configYamlToContinueConfig has cognitive complexity 55 (threshold 15). Drivers by points: if/else 15 (29 pts), ternaries 6 (15 pts), error handling 4 (5 pts), boolean chains 4, loops 2 (nesting depth added 24). Of this number, 37 points are the body's own statements and 18 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskManager.searchTasks (cognitive 55) manual-testing-sandbox/next-edit/next-edit-10-5.ts:332— TaskManager.searchTasks has cognitive complexity 55 (threshold 15). Drivers by points: if/else 18 (25 pts), ternaries 5 (16 pts), boolean chains 14 (nesting depth added 18). Most of this is not in the body itself: 4 of the 55 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 336, 402). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
migrateSharedConfig.migrateJsonSharedConfig (cognitive 54) core/config/migrateSharedConfig.ts:18— migrateSharedConfig.migrateJsonSharedConfig has cognitive complexity 54 (threshold 15). Drivers by points: if/else 31 (53 pts), error handling 1 (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.
Gemini.processGeminiResponse (cognitive 53) core/llm/llms/Gemini.ts:370— Gemini.processGeminiResponse has cognitive complexity 53 (threshold 15). Drivers by points: if/else 13 (31 pts), ternaries 2 (10 pts), loops 3 (7 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
refreshIndex.getAddRemoveForTag (cognitive 50) core/indexing/refreshIndex.ts:138— refreshIndex.getAddRemoveForTag has cognitive complexity 50 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 11 (21 pts), match/switch 1 (2 pts) (nesting depth added 26). Of this number, 46 points are the body's own statements and 4 belong to one function item inside it that branches. 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.
EditMessageSelector.EditMessageSelector (cognitive 49) extensions/cli/src/ui/EditMessageSelector.tsx:19— EditMessageSelector.EditMessageSelector has cognitive complexity 49 (threshold 15). Drivers by points: if/else 21 (26 pts), boolean chains 12, ternaries 5 (10 pts), loops 1 (nesting depth added 10). Most of this is not in the body itself: 4 of the 49 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 122, a function literal at line 80, renderEditText, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
QuizPrompt.QuizPrompt (cognitive 49) extensions/cli/src/ui/components/QuizPrompt.tsx:19— QuizPrompt.QuizPrompt has cognitive complexity 49 (threshold 15). Drivers by points: if/else 16 (26 pts), boolean chains 12, ternaries 5 (11 pts) (nesting depth added 16). Most of this is not in the body itself: 9 of the 49 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 36, 80, 89, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
GitLabMergeRequestContextProvider.getContextItems (cognitive 48) REDACTED:145— GitLabMergeRequestContextProvider.getContextItems has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (25 pts), ternaries 4 (12 pts), loops 4 (8 pts), boolean chains 2, error handling 1 (nesting depth added 26). Of this number, 30 points are the body's own statements and 18 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FindAndReplace.FindAndReplaceDisplay (cognitive 48) gui/src/pages/gui/ToolCallDiv/FindAndReplace.tsx:86— FindAndReplace.FindAndReplaceDisplay has cognitive complexity 48 (threshold 15). Drivers by points: if/else 16 (17 pts), ternaries 11 (17 pts), boolean chains 11, loops 1 (2 pts), error handling 1 (nesting depth added 8). Most of this is not in the body itself: 6 of the 48 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 288, a function literal at line 128, renderContainer, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DocsService.indexAndAdd (cognitive 47) core/indexing/docs/DocsService.ts:435— DocsService.indexAndAdd has cognitive complexity 47 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 6, error handling 3 (4 pts), loops 3, ternaries 2 (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.
OSRContextMenu.OSRContextMenu (cognitive 47) gui/src/components/OSRContextMenu.tsx:13— OSRContextMenu.OSRContextMenu has cognitive complexity 47 (threshold 15). Drivers by points: if/else 16 (33 pts), boolean chains 9, loops 1 (5 pts) (nesting depth added 21). Most of this is not in the body itself: 4 of the 47 points are its own statements and the rest belongs to 3 function items inside it that branch (a function literal at line 50, a function literal at line 43, onMenuItemClick). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
next-edit-6-3.searchFiles (cognitive 47) manual-testing-sandbox/next-edit/next-edit-6-3.ts:232— next-edit-6-3.searchFiles has cognitive complexity 47 (threshold 15). Drivers by points: if/else 15 (32 pts), boolean chains 10, loops 2 (5 pts) (nesting depth added 20). 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.
openaiToVercelMessages.convertOpenAIMessagesToVercel (cognitive 47) packages/openai-adapters/src/openaiToVercelMessages.ts:24— openaiToVercelMessages.convertOpenAIMessagesToVercel has cognitive complexity 47 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 4 (9 pts), error handling 1 (6 pts), ternaries 2 (6 pts), boolean chains 5, match/switch 1 (2 pts) (nesting depth added 28). 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.
validation.validateConfig (cognitive 46) core/config/validation.ts:10— validation.validateConfig has cognitive complexity 46 (threshold 15). Drivers by points: if/else 23 (38 pts), boolean chains 8 (nesting depth added 15). Of this number, 19 points are the body's own statements and 27 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StaticContextService.extractRelevantHeaders (cognitive 45) core/autocomplete/context/static-context/StaticContextService.ts:400— StaticContextService.extractRelevantHeaders has cognitive complexity 45 (threshold 15). Drivers by points: if/else 8 (28 pts), loops 4 (9 pts), error handling 1 (4 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 30). Of this number, 34 points are the body's own statements and 11 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Gemini.prepareBody (cognitive 45) core/llm/llms/Gemini.ts:234— Gemini.prepareBody has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (31 pts), boolean chains 6, ternaries 3 (5 pts), error handling 1 (3 pts) (nesting depth added 20). Most of this is not in the body itself: 9 of the 45 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 257, 291, 241, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
WatsonX._streamChat (cognitive 45) core/llm/llms/WatsonX.ts:265— WatsonX._streamChat has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (37 pts), error handling 1 (6 pts), boolean chains 1, loops 1 (nesting depth added 27). 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.
constructMessages.constructMessages (cognitive 45) gui/src/redux/util/constructMessages.ts:37— constructMessages.constructMessages has cognitive complexity 45 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 3 (6 pts), boolean chains 4, ternaries 1 (4 pts) (nesting depth added 22). Of this number, 44 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
handleApplyStateUpdate.handleApplyStateUpdate (cognitive 45) gui/src/redux/thunks/handleApplyStateUpdate.ts:27— handleApplyStateUpdate.handleApplyStateUpdate has cognitive complexity 45 (threshold 15). Drivers by points: if/else 14 (44 pts), boolean chains 1 (nesting depth added 30). 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.
BracketMatchingService.stopOnUnmatchedClosingBracket (cognitive 44) core/autocomplete/filtering/BracketMatchingService.ts:41— BracketMatchingService.stopOnUnmatchedClosingBracket has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (35 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 22). 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.
openaiTypeConverters.toResponsesInput (cognitive 44) core/llm/openaiTypeConverters.ts:986— openaiTypeConverters.toResponsesInput has cognitive complexity 44 (threshold 15). Drivers by points: if/else 10 (25 pts), boolean chains 8, ternaries 3 (8 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 21). Of this number, 43 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
errorAnalysis.analyzeError (cognitive 44) gui/src/util/errorAnalysis.ts:38— errorAnalysis.analyzeError has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (31 pts), boolean chains 9, ternaries 2 (4 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
doLoadConfig.doLoadConfig (cognitive 42) core/config/profile/doLoadConfig.ts:64— doLoadConfig.doLoadConfig has cognitive complexity 42 (threshold 15). Drivers by points: if/else 18 (25 pts), error handling 2 (6 pts), boolean chains 5, ternaries 1 (4 pts), loops 2 (nesting depth added 14). Of this number, 28 points are the body's own statements and 14 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
filterCodeBlock.filterCodeBlockLines (cognitive 41) core/autocomplete/filtering/streamTransforms/filterCodeBlock.ts:31— filterCodeBlock.filterCodeBlockLines has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (31 pts), boolean chains 7, loops 2 (3 pts) (nesting depth added 18). Of this number, 39 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
TipTapEditor.TipTapEditorInner (cognitive 41) gui/src/components/mainInput/TipTapEditor/TipTapEditor.tsx:48— TipTapEditor.TipTapEditorInner has cognitive complexity 41 (threshold 15). Drivers by points: if/else 24 (27 pts), boolean chains 12, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 7 of the 41 points are its own statements and the rest belongs to 15 function literals inside it that branch (lines 152, 226, 184, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Chat.Chat (cognitive 40) gui/src/pages/gui/Chat.tsx:106— Chat.Chat has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (18 pts), ternaries 9 (12 pts), boolean chains 10 (nesting depth added 6). Most of this is not in the body itself: 7 of the 40 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 267, 161, 138, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
openaiResponses.toResponsesInput (cognitive 40) packages/openai-adapters/src/apis/openaiResponses.ts:287— openaiResponses.toResponsesInput has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (32 pts), ternaries 1 (4 pts), boolean chains 3, loops 1 (nesting depth added 24). Of this number, 30 points are the body's own statements and 10 belong to one function literal inside it that branches. 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.
evaluateTerminalCommandSecurity.isCriticalCommand (cognitive 40) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:402— evaluateTerminalCommandSecurity.isCriticalCommand has cognitive complexity 40 (threshold 15). Drivers by points: if/else 19 (25 pts), boolean chains 15 (nesting depth added 6). Of this number, 38 points are the body's own statements and 2 belong to 5 function literals inside it that branch. 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.
index.StepContainerPreToolbar (cognitive 39) gui/src/components/StyledMarkdownPreview/StepContainerPreToolbar/index.tsx:43— index.StepContainerPreToolbar has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (18 pts), ternaries 9 (12 pts), boolean chains 9 (nesting depth added 5). Of this number, 16 points are the body's own statements and 23 belong to 9 function items inside it that branch. 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.
index.postprocessCompletion (cognitive 38) core/autocomplete/postprocessing/index.ts:92— index.postprocessCompletion has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 10 (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.
filtering.getSnippets (cognitive 38) core/autocomplete/templating/filtering.ts:44— filtering.getSnippets has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (28 pts), loops 3 (7 pts), boolean chains 2, ternaries 1 (nesting depth added 22). Of this number, 36 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
callTool.callToolFromUri (cognitive 37) core/tools/callTool.ts:67— callTool.callToolFromUri has cognitive complexity 37 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 1 (4 pts), error handling 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 20). Of this number, 30 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JobsSelector.JobsSelector (cognitive 37) extensions/cli/src/ui/JobsSelector.tsx:29— JobsSelector.JobsSelector has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 12, ternaries 5 (7 pts) (nesting depth added 7). Most of this is not in the body itself: 6 of the 37 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 51, 37, 180, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
VsCodeIde.getFileResults (cognitive 37) extensions/vscode/src/VsCodeIde.ts:476— VsCodeIde.getFileResults has cognitive complexity 37 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 3 (8 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 19). Of this number, 19 points are the body's own statements and 18 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
countTokens.countToolsTokens (cognitive 36) core/llm/countTokens.ts:135— countTokens.countToolsTokens has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (23 pts), loops 3 (10 pts), boolean chains 3 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Bedrock._streamChat (cognitive 36) core/llm/llms/Bedrock.ts:107— Bedrock._streamChat has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (30 pts), boolean chains 3, error handling 1, loops 1, ternaries 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.
Core.handleFilesChanged (cognitive 36) core/core.ts:1242— Core.handleFilesChanged has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (28 pts), error handling 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 22). 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.
loadJsonMcpConfigs.loadJsonMcpConfigs (cognitive 36) core/context/mcp/json/loadJsonMcpConfigs.ts:27— loadJsonMcpConfigs.loadJsonMcpConfigs has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (21 pts), ternaries 3 (7 pts), error handling 3 (4 pts), loops 2 (4 pts) (nesting depth added 18). Of this number, 29 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddModelForm.AddModelForm (cognitive 36) gui/src/forms/AddModelForm.tsx:33— AddModelForm.AddModelForm has cognitive complexity 36 (threshold 15). Drivers by points: boolean chains 20, if/else 7, ternaries 7, error handling 1, loops 1. Of this number, 21 points are the body's own statements and 15 belong to 12 function items inside it that branch. 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.
remarkTables.remarkTables (cognitive 36) gui/src/components/StyledMarkdownPreview/utils/remarkTables.tsx:23— remarkTables.remarkTables has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (31 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 14). None of this is in the body itself: all 36 points belong to 4 function literals inside it that branch (lines 140, 25, 83, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
fetch.fetchwithRequestOptions (cognitive 36) packages/fetch/src/fetch.ts:82— fetch.fetchwithRequestOptions has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 6, loops 2 (6 pts), ternaries 4 (5 pts), error handling 2 (nesting depth added 9). 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.
StaticContextService.extractRelevantTypesHelper (cognitive 35) core/autocomplete/context/static-context/StaticContextService.ts:303— StaticContextService.extractRelevantTypesHelper has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (30 pts), error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
myers.myersCharDiff (cognitive 35) core/diff/myers.ts:59— myers.myersCharDiff has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (31 pts), loops 2 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodebaseIndexer.indexFiles (cognitive 35) core/indexing/CodebaseIndexer.ts:552— CodebaseIndexer.indexFiles has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 4 (15 pts), loops 3 (8 pts), error handling 2 (6 pts), if/else 3 (6 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolResultSummary.ToolResultSummary (cognitive 35) extensions/cli/src/ui/ToolResultSummary.tsx:18— ToolResultSummary.ToolResultSummary has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 12 (29 pts), if/else 18 (24 pts), boolean chains 3, match/switch 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ToolResultSummary.ToolResultSummary::getSummary) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
RepoMapGenerator.generate (cognitive 34) core/util/generateRepoMap.ts:52— RepoMapGenerator.generate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 3 (9 pts), error handling 1 (4 pts) (nesting depth added 20). 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.
retry.withRetry (cognitive 34) core/llm/utils/retry.ts:209— retry.withRetry has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (21 pts), error handling 2 (6 pts), loops 2 (4 pts), boolean chains 2, ternaries 1 (nesting depth added 18). None of this is in the body itself: all 34 points belong to 3 function literals inside it that branch (lines 234, 279, 212). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
hookRunner.aggregateResults (cognitive 34) extensions/cli/src/hooks/hookRunner.ts:333— hookRunner.aggregateResults has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (26 pts), boolean chains 5, match/switch 1 (2 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
getTheme.getTheme (cognitive 34) extensions/vscode/src/util/getTheme.ts:56— getTheme.getTheme has cognitive complexity 34 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 3 (9 pts), boolean chains 6, error handling 1, 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.
editOutcomeLogger.extractPromptAndCompletion (cognitive 34) gui/src/util/editOutcomeLogger.ts:55— editOutcomeLogger.extractPromptAndCompletion has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 7 (23 pts), boolean chains 5, if/else 2 (4 pts), loops 1 (2 pts) (nesting depth added 19). Most of this is not in the body itself: 15 of the 34 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 84, 97, 64). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
VertexAI.constructor (cognitive 33) core/llm/llms/VertexAI.ts:61— VertexAI.constructor has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (27 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VsCodeExtension.constructor (cognitive 33) REDACTED:172— VsCodeExtension.constructor has cognitive complexity 33 (threshold 15). Drivers by points: if/else 20 (28 pts), boolean chains 2, ternaries 2, loops 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 33 points are its own statements and the rest belongs to 13 function items inside it that branch (a function literal at line 564, getUsingFullFileDiff, a function literal at line 621, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
agentFiles.parseAgentFileTools (cognitive 32) packages/config-yaml/src/markdown/agentFiles.ts:102— agentFiles.parseAgentFileTools has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (29 pts), boolean chains 2, 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.
evaluateTerminalCommandSecurity.isSafeCommand (cognitive 32) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:979— evaluateTerminalCommandSecurity.isSafeCommand has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 9 (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.
BaseNextEditModelProvider.calculateOptimalEditableRegion (cognitive 31) core/nextEdit/providers/BaseNextEditProvider.ts:382— BaseNextEditModelProvider.calculateOptimalEditableRegion has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 3 (9 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
handleToolCalls.handleToolCalls (cognitive 31) extensions/cli/src/stream/handleToolCalls.ts:36— handleToolCalls.handleToolCalls has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 8, ternaries 1 (2 pts) (nesting depth added 10). Of this number, 20 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openaiResponses.collectAssistantContentParts (cognitive 31) packages/openai-adapters/src/apis/openaiResponses.ts:157— openaiResponses.collectAssistantContentParts has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
evaluateTerminalCommandSecurity.evaluateTokens (cognitive 31) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:176— evaluateTerminalCommandSecurity.evaluateTokens has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (28 pts), loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
markdown.markdownChunker (cognitive 30) core/indexing/chunk/markdown.ts:61— markdown.markdownChunker has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (9 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodebaseIndexer.refreshDirs (cognitive 30) core/indexing/CodebaseIndexer.ts:334— CodebaseIndexer.refreshDirs has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 3 (5 pts), ternaries 2, boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
streamChat.llmStreamChat (cognitive 30) core/llm/streamChat.ts:9— streamChat.llmStreamChat has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (24 pts), loops 2 (4 pts), boolean chains 1, error handling 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.
NextEditEditableRegionCalculator.staticRerankJump (cognitive 30) core/nextEdit/NextEditEditableRegionCalculator.ts:247— NextEditEditableRegionCalculator.staticRerankJump has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 10, error handling 2, loops 1 (nesting depth added 4). Of this number, 25 points are the body's own statements and 5 belong to 2 function literals inside it that branch. 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.
exponentialBackoff.withExponentialBackoff (cognitive 30) extensions/cli/src/util/exponentialBackoff.ts:249— exponentialBackoff.withExponentialBackoff has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (25 pts), loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
streamChatResponse.helpers.executeStreamedToolCalls (cognitive 30) extensions/cli/src/stream/streamChatResponse.helpers.ts:469— streamChatResponse.helpers.executeStreamedToolCalls has cognitive complexity 30 (threshold 15). Drivers by points: error handling 7 (17 pts), ternaries 3 (9 pts), if/else 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 17). Of this number, 20 points are the body's own statements and 10 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VerticalDiffManager.streamEdit (cognitive 30) extensions/vscode/src/diff/vertical/manager.ts:357— VerticalDiffManager.streamEdit has cognitive complexity 30 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 6, error handling 1, loops 1, ternaries 1 (nesting depth added 7). Of this number, 23 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TaskManager.updateTask (cognitive 30) manual-testing-sandbox/next-edit/next-edit-10-5.ts:186— TaskManager.updateTask has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 8 (nesting depth added 9). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AskSageApi.convertMessages (cognitive 30) packages/openai-adapters/src/apis/AskSage.ts:139— AskSageApi.convertMessages has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 5 (17 pts), if/else 7 (12 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
loadMarkdownRules.loadMarkdownRules (cognitive 29) core/config/markdown/loadMarkdownRules.ts:15— loadMarkdownRules.loadMarkdownRules has cognitive complexity 29 (threshold 15). Drivers by points: error handling 3 (8 pts), if/else 3 (8 pts), ternaries 2 (7 pts), loops 4 (6 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
streamMarkdownUtils.stopAtLinesWithMarkdownSupport (cognitive 29) core/utils/streamMarkdownUtils.ts:39— streamMarkdownUtils.stopAtLinesWithMarkdownSupport has cognitive complexity 29 (threshold 15). Drivers by points: loops 8 (17 pts), if/else 6 (12 pts) (nesting depth added 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
tree-sitter-utils.extractTopLevelDeclsWithFormatting (cognitive 29) core/autocomplete/context/static-context/tree-sitter-utils.ts:81— tree-sitter-utils.extractTopLevelDeclsWithFormatting has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (23 pts), boolean chains 3, loops 2 (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.
Anthropic.handleResponse (cognitive 29) core/llm/llms/Anthropic.ts:265— Anthropic.handleResponse has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (18 pts), match/switch 2 (5 pts), ternaries 2 (4 pts), boolean chains 1, 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.
BaseLLM.fetch::customFetch (cognitive 29) core/llm/index.ts:451— BaseLLM.fetch::customFetch has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (21 pts), ternaries 1 (4 pts), boolean chains 3, error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
systemMessage.loadMarkdownRulesWithMetadata (cognitive 29) extensions/cli/src/systemMessage.ts:89— systemMessage.loadMarkdownRulesWithMetadata has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (14 pts), error handling 3 (8 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
systemMessage.constructSystemMessage (cognitive 29) extensions/cli/src/systemMessage.ts:161— systemMessage.constructSystemMessage has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (16 pts), error handling 2 (4 pts), loops 3 (4 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SessionSelector.SessionSelector (cognitive 29) extensions/cli/src/ui/SessionSelector.tsx:39— SessionSelector.SessionSelector has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 10, ternaries 6 (8 pts) (nesting depth added 3). Most of this is not in the body itself: 6 of the 29 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 94, 145, 49, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Selector.Selector (cognitive 29) extensions/cli/src/ui/Selector.tsx:30— Selector.Selector has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 9, ternaries 5 (8 pts) (nesting depth added 5). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 53, a function literal at line 44, defaultRenderOption, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
VsCodeWebviewProtocol.webview::handleMessage (cognitive 29) REDACTED:51— VsCodeWebviewProtocol.webview::handleMessage has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 4, loops 2 (4 pts), error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JumpManager.suggestJump (cognitive 29) extensions/vscode/src/activation/JumpManager.ts:185— JumpManager.suggestJump has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 1 (4 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnthropicApi.convertMessageContentToBlocks (cognitive 29) packages/openai-adapters/src/apis/Anthropic.ts:184— AnthropicApi.convertMessageContentToBlocks has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (22 pts), ternaries 1 (4 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 17). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
diffFormatting.extractMetadataFromUnifiedDiff (cognitive 28) core/nextEdit/context/diffFormatting.ts:138— diffFormatting.extractMetadataFromUnifiedDiff has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 4, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Ollama._streamChat (cognitive 28) core/llm/llms/Ollama.ts:496— Ollama._streamChat has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (31 pts), loops 4 (12 pts), error handling 1 (5 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 28). 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. This shape REPEATS in the file: one other method here (Ollama._streamChat::convertChatMessage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SyntaxHighlighter.highlightCode::processNode (cognitive 28) extensions/cli/src/ui/SyntaxHighlighter.ts:98— SyntaxHighlighter.highlightCode::processNode has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 2 (5 pts), boolean chains 3 (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.
MCPAppRenderer.McpAppRenderer (cognitive 28) gui/src/pages/gui/ToolCallDiv/MCPAppRenderer.tsx:92— MCPAppRenderer.McpAppRenderer has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 9, if/else 9, ternaries 4 (7 pts), error handling 3 (nesting depth added 3). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 11 function literals inside it that branch (lines 277, 303, 314, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FileStorageManager.matchesQuery (cognitive 28) manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts:402— FileStorageManager.matchesQuery has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 9, loops 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openaiTypeConverters.sanitizeResponsesInput (cognitive 27) core/llm/openaiTypeConverters.ts:926— openaiTypeConverters.sanitizeResponsesInput has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 4 (6 pts), boolean chains 2 (nesting depth added 11). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
autodetect.autodetectTemplateType (cognitive 27) core/llm/autodetect.ts:313— autodetect.autodetectTemplateType has cognitive complexity 27 (threshold 15). Drivers by points: if/else 22, boolean chains 5. 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.
Ollama._streamChat::convertChatMessage (cognitive 27) core/llm/llms/Ollama.ts:539— Ollama._streamChat::convertChatMessage has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (21 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (Ollama._streamChat) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
MCPService.getConnectedClient (cognitive 27) extensions/cli/src/services/MCPService.ts:401— MCPService.getConnectedClient has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (20 pts), error handling 2 (5 pts), boolean chains 2 (nesting depth added 13). Most of this is not in the body itself: 13 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 417). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
renderReport.renderTextReport (cognitive 27) extensions/cli/src/commands/review/renderReport.ts:71— renderReport.renderTextReport has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 5 (12 pts), boolean chains 2, loops 1 (nesting depth added 12). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useChat.useChat (cognitive 27) extensions/cli/src/ui/hooks/useChat.ts:48— useChat.useChat has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 11, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 3 of the 27 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 77, 269, 175, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
RulesSection.RulesSubSection (cognitive 27) gui/src/pages/config/sections/RulesSection.tsx:420— RulesSection.RulesSubSection has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (18 pts), boolean chains 3, error handling 1 (2 pts), loops 1 (2 pts), ternaries 2 (nesting depth added 14). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 446, handleAddRule). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
LanceDbIndex.update (cognitive 26) core/indexing/LanceDbIndex.ts:254— LanceDbIndex.update has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 4 (6 pts), error handling 1 (3 pts) (nesting depth added 10). Of this number, 19 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SageMaker._streamComplete (cognitive 26) core/llm/llms/SageMaker.ts:34— SageMaker._streamComplete has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (5 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (SageMaker._streamChat) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SageMaker._streamChat (cognitive 26) core/llm/llms/SageMaker.ts:82— SageMaker._streamChat has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 2 (5 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (SageMaker._streamComplete) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
MemoizedMessage.MemoizedMessage (cognitive 26) extensions/cli/src/ui/components/MemoizedMessage.tsx:51— MemoizedMessage.MemoizedMessage has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 8 (16 pts), boolean chains 7, if/else 3 (nesting depth added 8). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to one function literal inside it that branches (line 99). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
session.saveCurrentSession (cognitive 26) gui/src/redux/thunks/session.ts:192— session.saveCurrentSession has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, error handling 1 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LumpToolbar.LumpToolbar (cognitive 26) gui/src/components/mainInput/Lump/LumpToolbar/LumpToolbar.tsx:49— LumpToolbar.LumpToolbar has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (21 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 5). Most of this is not in the body itself: 11 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 129, handleStopAction, a function literal at line 124, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MarkdownBlockStateTracker.shouldStopAtPosition (cognitive 25) core/utils/markdownUtils.ts:61— MarkdownBlockStateTracker.shouldStopAtPosition has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (24 pts), 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.
OpenAI._streamResponses (cognitive 25) core/llm/llms/OpenAI.ts:571— OpenAI._streamResponses has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (7 pts), error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
code.collapseChildren (cognitive 25) core/indexing/chunk/code.ts:26— code.collapseChildren has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (5 pts), boolean chains 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.
CheerioCrawler.crawl (cognitive 25) core/indexing/docs/crawlers/CheerioCrawler.ts:27— CheerioCrawler.crawl has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (15 pts), loops 3 (7 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ServiceDebugger.ServiceDebugger (cognitive 25) extensions/cli/src/ui/ServiceDebugger.tsx:29— ServiceDebugger.ServiceDebugger has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 12 (17 pts), boolean chains 5, if/else 2, match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 9 of the 25 points are its own statements and the rest belongs to 3 function items inside it that branch (getServiceDetails, getServiceStatus, a function literal at line 85). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
lsp.getDefinitionsForNode (cognitive 25) extensions/vscode/src/autocomplete/lsp.ts:228— lsp.getDefinitionsForNode has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (22 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
findWidgetSearch.searchWithinContainer (cognitive 25) gui/src/components/find/findWidgetSearch.ts:20— findWidgetSearch.searchWithinContainer has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 5 (8 pts), loops 2, boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 6 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 45, 70, 134). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Cohere._convertMessages (cognitive 24) core/llm/llms/Cohere.ts:20— Cohere._convertMessages has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (21 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 13). Of this number, 21 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
findSearchMatch.findFuzzyMatch (cognitive 24) core/edit/searchAndReplace/findSearchMatch.ts:224— findSearchMatch.findFuzzyMatch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 3 (5 pts), boolean chains 4 (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.
CompletionProvider.provideInlineCompletionItems (cognitive 24) core/autocomplete/CompletionProvider.ts:150— CompletionProvider.provideInlineCompletionItems has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (16 pts), ternaries 2 (3 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
util.convertSingleToDoubleQuoteJSON (cognitive 24) extensions/vscode/src/util/util.ts:15— util.convertSingleToDoubleQuoteJSON has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 2, loops 1 (nesting depth added 11). Of this number, 23 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
renderSlashCommand.renderSlashCommandPrompt (cognitive 24) gui/src/components/mainInput/TipTapEditor/utils/renderSlashCommand.ts:13— renderSlashCommand.renderSlashCommandPrompt has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 3 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolPolicyItem.ToolPolicyItem (cognitive 24) gui/src/pages/config/components/ToolPolicyItem.tsx:29— ToolPolicyItem.ToolPolicyItem has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 11 (13 pts), boolean chains 7, if/else 4 (nesting depth added 2). Of this number, 20 points are the body's own statements and 4 belong to 3 function literals inside it that branch. 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.
useTotalUsage.useTotalUsage (cognitive 24) gui/src/hooks/useTotalUsage.ts:25— useTotalUsage.useTotalUsage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 4 (14 pts), boolean chains 6, match/switch 1 (3 pts), loops 1 (nesting depth added 12). None of this is in the body itself: all 24 points belong to one function literal inside it that branches (line 26). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
util.customFetch::letRequestOptionsOverrideAuthHeaders (cognitive 24) packages/openai-adapters/src/util.ts:162— util.customFetch::letRequestOptionsOverrideAuthHeaders has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 6 (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.
BedrockApi.chatCompletionStream (cognitive 24) packages/openai-adapters/src/apis/Bedrock.ts:476— BedrockApi.chatCompletionStream has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (22 pts), error handling 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
VertexAIApi.setupAuthentication (cognitive 24) packages/openai-adapters/src/apis/VertexAI.ts:72— VertexAIApi.setupAuthentication has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, error handling 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.
sharedConfig.modifyAnyConfigWithSharedConfig (cognitive 23) core/config/sharedConfig.ts:91— sharedConfig.modifyAnyConfigWithSharedConfig has cognitive complexity 23 (threshold 15). Drivers by points: if/else 23. 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.
openaiTypeConverters.mergeReasoningDetails (cognitive 23) core/llm/openaiTypeConverters.ts:743— openaiTypeConverters.mergeReasoningDetails has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (4 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.
BaseLLM.streamComplete (cognitive 23) core/llm/index.ts:703— BaseLLM.streamComplete has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 2 (5 pts), boolean chains 2, error handling 1, ternaries 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.
streamLazyApply.streamFillUnchangedCode (cognitive 23) core/edit/lazy/streamLazyApply.ts:72— streamLazyApply.streamFillUnchangedCode has cognitive complexity 23 (threshold 15). Drivers by points: loops 5 (13 pts), if/else 6 (10 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
retry.defaultShouldRetry (cognitive 23) core/llm/utils/retry.ts:42— retry.defaultShouldRetry has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 10 (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.
formatError.formatError (cognitive 23) extensions/cli/src/util/formatError.ts:4— formatError.formatError has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
review.review (cognitive 23) extensions/cli/src/commands/review.ts:261— review.review has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2 (4 pts), boolean chains 3, ternaries 2 (3 pts), error handling 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
serve.serve::processMessages (cognitive 23) REDACTED:448— serve.serve::processMessages has cognitive complexity 23 (threshold 15). Drivers by points: error handling 5 (14 pts), if/else 4 (7 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useUserInput.handleControlKeys (cognitive 23) extensions/cli/src/ui/hooks/useUserInput.ts:23— useUserInput.handleControlKeys has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 6 (nesting depth added 7). Of this number, 14 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useChat.helpers.processSlashCommandResult (cognitive 23) extensions/cli/src/ui/hooks/useChat.helpers.ts:58— useChat.helpers.processSlashCommandResult has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 6, ternaries 1 (2 pts) (nesting depth added 3). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
errorHandling.handleLLMError (cognitive 23) extensions/vscode/src/util/errorHandling.ts:9— errorHandling.handleLLMError has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 5 (nesting depth added 3). Of this number, 16 points are the body's own statements and 7 belong to 2 function literals inside it that branch. 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.
stream.streamResponse (cognitive 23) packages/fetch/src/stream.ts:10— stream.streamResponse has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (4 pts), error handling 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.
GeminiApi.processStreamResponse (cognitive 23) packages/openai-adapters/src/apis/Gemini.ts:324— GeminiApi.processStreamResponse has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
evaluateTerminalCommandSecurity.isHighRiskCommand (cognitive 23) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:942— evaluateTerminalCommandSecurity.isHighRiskCommand has cognitive complexity 23 (threshold 15). Drivers by points: if/else 23. 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.
index.validateFilesPresent (cognitive 22) REDACTED:42— index.validateFilesPresent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 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.
lineStream.stopAtLines (cognitive 22) core/autocomplete/filtering/streamTransforms/lineStream.ts:353— lineStream.stopAtLines has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (19 pts), 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.
autodetect.autodetectPromptTemplates (cognitive 22) core/llm/autodetect.ts:471— autodetect.autodetectPromptTemplates has cognitive complexity 22 (threshold 15). Drivers by points: if/else 20 (21 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
countTokens.extractToolSequence (cognitive 22) core/llm/countTokens.ts:228— countTokens.extractToolSequence has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (7 pts), boolean chains 5 (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.
DocsService.syncDocs (cognitive 22) core/indexing/docs/DocsService.ts:927— DocsService.syncDocs has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Bedrock._convertMessageContentToBlocks (cognitive 22) core/llm/llms/Bedrock.ts:550— Bedrock._convertMessageContentToBlocks has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Cohere._streamChat (cognitive 22) core/llm/llms/Cohere.ts:155— Cohere._streamChat has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts), match/switch 1 (2 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.
deterministic.findLazyBlockReplacements (cognitive 22) core/edit/lazy/deterministic.ts:353— deterministic.findLazyBlockReplacements has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
retry.createRetryableAsyncGenerator (cognitive 22) core/llm/utils/retry.ts:333— retry.createRetryableAsyncGenerator has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (7 pts), error handling 2 (4 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.
streamChatResponse.processStreamingResponse (cognitive 22) extensions/cli/src/stream/streamChatResponse.ts:197— streamChatResponse.processStreamingResponse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 2, error handling 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.
ToolPermissionSelector.ToolPermissionSelector (cognitive 22) extensions/cli/src/ui/components/ToolPermissionSelector.tsx:57— ToolPermissionSelector.ToolPermissionSelector has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11, boolean chains 8, ternaries 3. Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 74, 145). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
StreamError.StreamErrorDialog (cognitive 22) gui/src/pages/gui/StreamError.tsx:26— StreamError.StreamErrorDialog has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, if/else 8 (9 pts), ternaries 3, loops 1 (nesting depth added 1). Of this number, 15 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
processEditorContent.processEditorContent (cognitive 22) gui/src/components/mainInput/TipTapEditor/utils/processEditorContent.ts:55— processEditorContent.processEditorContent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParallelListeners.ParallelListeners (cognitive 22) gui/src/hooks/ParallelListeners.tsx:37— ParallelListeners.ParallelListeners has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 5, ternaries 1 (nesting depth added 2). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 56, 106, 127, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
InMemoryTaskRepository.matchesSearchCriteria (cognitive 22) manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:296— InMemoryTaskRepository.matchesSearchCriteria has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 10 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
openaiResponses.fromResponsesChunk (cognitive 22) packages/openai-adapters/src/apis/openaiResponses.ts:575— openaiResponses.fromResponsesChunk has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (21 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.
openaiTypeConverters.handleOutputItemAdded (cognitive 21) core/llm/openaiTypeConverters.ts:437— openaiTypeConverters.handleOutputItemAdded has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
streamDiff.streamDiff (cognitive 21) core/diff/streamDiff.ts:14— streamDiff.streamDiff has cognitive complexity 21 (threshold 15). Drivers by points: loops 4 (8 pts), if/else 5 (7 pts), boolean chains 4, 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.
autocompleteContextFetching.getAutocompleteContext (cognitive 21) core/nextEdit/context/autocompleteContextFetching.ts:34— autocompleteContextFetching.getAutocompleteContext has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
load.loadContinueConfigFromJson (cognitive 21) core/config/load.ts:791— load.loadContinueConfigFromJson has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 4 (9 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
deterministic.deterministicApplyLazyEdit (cognitive 21) core/edit/lazy/deterministic.ts:129— deterministic.deterministicApplyLazyEdit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (21 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
checks.listChecks (cognitive 21) REDACTED:146— checks.listChecks has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 2 (7 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity· index.addCommonOptions().argument("[prompt]","Optional prompt to send to the assistant").option("-p, --print","Print response (cognitive 21) · ×1
index.addCommonOptions().argument("[prompt]","Optional prompt to send to the assistant").option("-p, --print","Print response (cognitive 21) extensions/cli/src/index.ts:199— index.addCommonOptions().argument("[prompt]","Optional prompt to send to the assistant").option("-p, --print","Print response has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NextEditWindowManager.createSyntaxHighlightedLine (cognitive 21) extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditWindowManager.kt:348— NextEditWindowManager.createSyntaxHighlightedLine has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseLLM.streamFim (cognitive 20) core/llm/index.ts:587— BaseLLM.streamFim has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), boolean chains 2, error handling 1, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
exponentialBackoff.chatCompletionStreamWithBackoff (cognitive 20) extensions/cli/src/util/exponentialBackoff.ts:169— exponentialBackoff.chatCompletionStreamWithBackoff has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (16 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolResultSummary.ToolResultSummary::getSummary (cognitive 20) extensions/cli/src/ui/ToolResultSummary.tsx:170— ToolResultSummary.ToolResultSummary::getSummary has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 6 (8 pts), match/switch 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ToolResultSummary.ToolResultSummary) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
chat.runHeadlessMode (cognitive 20) extensions/cli/src/commands/chat.ts:436— chat.runHeadlessMode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7, ternaries 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NextEditWindowManager.showNextEditWindow (cognitive 20) extensions/vscode/src/activation/NextEditWindowManager.ts:332— NextEditWindowManager.showNextEditWindow has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, error handling 2 (3 pts) (nesting depth added 5). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConfigYamlDocumentLinkProvider.provideDocumentLinks (cognitive 20) REDACTED:9— ConfigYamlDocumentLinkProvider.provideDocumentLinks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
patchNestedMarkdown.patchNestedMarkdown (cognitive 20) gui/src/components/StyledMarkdownPreview/utils/patchNestedMarkdown.ts:15— patchNestedMarkdown.patchNestedMarkdown has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.StyledMarkdownPreview (cognitive 20) gui/src/components/StyledMarkdownPreview/index.tsx:188— index.StyledMarkdownPreview has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, ternaries 3 (nesting depth added 3). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 333, 240, 292, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FindWidget.useFindWidget (cognitive 20) gui/src/components/find/FindWidget.tsx:58— FindWidget.useFindWidget has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 3 (nesting depth added 3). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 115, 191, 201). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
StepContainer.StepContainer (cognitive 20) REDACTED:21— StepContainer.StepContainer has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 14, if/else 3 (4 pts), ternaries 2 (nesting depth added 1). Of this number, 14 points are the body's own statements and 6 belong to one function literal inside it that branches. 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.
resolveEditorContent.gatherContextItems (cognitive 20) gui/src/components/mainInput/TipTapEditor/utils/resolveEditorContent.ts:111— resolveEditorContent.gatherContextItems has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6, loops 1 (nesting depth added 5). Of this number, 14 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrateLocalStorage.migrateToolPolicies (cognitive 20) gui/src/util/migrateLocalStorage.ts:11— migrateLocalStorage.migrateToolPolicies has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 1 (4 pts), boolean chains 1 (nesting depth added 13). Of this number, 10 points are the body's own statements and 10 belong to one function literal inside it that branches. 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.
vercelStreamConverter.convertVercelStreamPart (cognitive 20) packages/openai-adapters/src/vercelStreamConverter.ts:83— vercelStreamConverter.convertVercelStreamPart has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 2 (4 pts), match/switch 1 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
OpenRouterCaching.applyAnthropicCachingToOpenRouterBody (cognitive 20) packages/openai-adapters/src/apis/OpenRouterCaching.ts:154— OpenRouterCaching.applyAnthropicCachingToOpenRouterBody has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 225, 172, 203, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
index.dedentAndGetCommonWhitespace (cognitive 19) core/util/index.ts:30— index.dedentAndGetCommonWhitespace has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.dedent (cognitive 19) core/util/index.ts:139— index.dedent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 3 (6 pts), boolean chains 3, loops 3 (nesting depth added 6). Of this number, 16 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openaiTypeConverters.toChatMessage (cognitive 19) core/llm/openaiTypeConverters.ts:109— openaiTypeConverters.toChatMessage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 6). Of this number, 16 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
openaiTypeConverters.convertThinkingMessageToReasoningItem (cognitive 19) core/llm/openaiTypeConverters.ts:845— openaiTypeConverters.convertThinkingMessageToReasoningItem has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 6, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CodeSnippetsCodebaseIndex.update (cognitive 19) core/indexing/CodeSnippetsIndex.ts:211— CodeSnippetsCodebaseIndex.update has cognitive complexity 19 (threshold 15). Drivers by points: loops 6 (8 pts), if/else 3 (7 pts), error handling 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Anthropic.convertMessageContentToBlocks (cognitive 19) core/llm/llms/Anthropic.ts:88— Anthropic.convertMessageContentToBlocks has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Gemini.removeSystemMessage (cognitive 19) core/llm/llms/Gemini.ts:101— Gemini.removeSystemMessage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 6 (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.
streamDiffLines.streamDiffLines (cognitive 19) core/edit/streamDiffLines.ts:77— streamDiffLines.streamDiffLines has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (4 pts), boolean chains 3, loops 1 (nesting depth added 4). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
merge.mergeJson (cognitive 19) core/util/merge.ts:5— merge.mergeJson has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 7). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
findSearchMatch.jaroSimilarity (cognitive 19) core/edit/searchAndReplace/findSearchMatch.ts:148— findSearchMatch.jaroSimilarity has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (6 pts), boolean chains 2 (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.
deterministic.reconstructNewFile (cognitive 19) core/edit/lazy/deterministic.ts:23— deterministic.reconstructNewFile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 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.
streamChatResponse.streamChatResponse (cognitive 19) extensions/cli/src/stream/streamChatResponse.ts:423— streamChatResponse.streamChatResponse has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelSelect.ModelSelect (cognitive 19) gui/src/components/modelSelection/ModelSelect.tsx:120— ModelSelect.ModelSelect has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 4 (6 pts), boolean chains 4 (nesting depth added 4). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 172, 237). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
InputToolbar.InputToolbar (cognitive 19) gui/src/components/mainInput/InputToolbar.tsx:49— InputToolbar.InputToolbar has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 14, ternaries 3 (4 pts), if/else 1 (nesting depth added 1). Of this number, 14 points are the body's own statements and 5 belong to 3 function literals inside it that branch. 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.
ContinueInputBox.ContinueInputBox (cognitive 19) gui/src/components/mainInput/ContinueInputBox.tsx:55— ContinueInputBox.ContinueInputBox has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (9 pts), boolean chains 7, if/else 3 (nesting depth added 2). Of this number, 12 points are the body's own statements and 7 belong to 4 function literals inside it that branch. 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.
ModelRoleSelector.ModelRoleSelector (cognitive 19) gui/src/pages/config/components/ModelRoleSelector.tsx:31— ModelRoleSelector.ModelRoleSelector has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (9 pts), boolean chains 5, if/else 3 (5 pts) (nesting depth added 7). Of this number, 12 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RulesSection.PromptsSubSection (cognitive 19) gui/src/pages/config/sections/RulesSection.tsx:285— RulesSection.PromptsSubSection has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 8). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 306, 330). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ToolsSection.MCPServerPreview (cognitive 19) gui/src/pages/config/sections/ToolsSection.tsx:61— ToolsSection.MCPServerPreview has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 12, if/else 4, ternaries 3. Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 7 function items inside it that branch (ResourceRow, onRefresh, a function literal at line 283, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
index.listAvailableSecrets (cognitive 19) packages/config-yaml/src/interfaces/index.ts:85— index.listAvailableSecrets has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (3 pts), match/switch 1 (3 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.
validation.validateConfigYaml (cognitive 19) packages/config-yaml/src/validation.ts:21— validation.validateConfigYaml has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 1 (2 pts), error handling 1 (nesting depth added 5). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to one function literal inside it that branches (line 37). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
NextEditWindowManager.calculateCharDiff (cognitive 19) extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditWindowManager.kt:590— NextEditWindowManager.calculateCharDiff has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MCPOauth.handleMCPOauthCode (cognitive 18) core/context/mcp/MCPOauth.ts:276— MCPOauth.handleMCPOauthCode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StaticContextService.generateTargetTypesHelper (cognitive 18) core/autocomplete/context/static-context/StaticContextService.ts:606— StaticContextService.generateTargetTypesHelper has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelService.doInitialize (cognitive 18) extensions/cli/src/services/ModelService.ts:41— ModelService.doInitialize has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 6 (nesting depth added 4). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TelemetryService.initialize (cognitive 18) extensions/cli/src/telemetry/telemetryService.ts:98— TelemetryService.initialize has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 2 (6 pts), match/switch 1 (2 pts), error handling 1, loops 1 (nesting depth added 5). Of this number, 10 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
historySplitting.splitContentIntoHistoryItems (cognitive 18) extensions/cli/src/ui/utils/historySplitting.ts:50— historySplitting.splitContentIntoHistoryItems has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (17 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.
MarkdownRenderer.MarkdownRenderer (cognitive 18) extensions/cli/src/ui/MarkdownRenderer.tsx:22— MarkdownRenderer.MarkdownRenderer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, loops 3 (nesting depth added 2). None of this is in the body itself: all 18 points belong to 5 function items inside it that branch (renderMarkdown, a function literal at line 127, a function literal at line 184, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TUIChat.TUIChat (cognitive 18) extensions/cli/src/ui/TUIChat.tsx:152— TUIChat.TUIChat has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 15, error handling 1, if/else 1, ternaries 1. Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
statusBar.setupStatusBar (cognitive 18) extensions/vscode/src/autocomplete/statusBar.ts:119— statusBar.setupStatusBar has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 7). Of this number, 9 points are the body's own statements and 9 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CapturedTerminal.constructor (cognitive 18) extensions/vscode/src/terminal/terminalEmulator.ts:165— CapturedTerminal.constructor has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 189, 203, 212). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ThinkingBlockPeek.ThinkingBlockPeek (cognitive 18) gui/src/components/mainInput/belowMainInput/ThinkingBlockPeek.tsx:28— ThinkingBlockPeek.ThinkingBlockPeek has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7 (15 pts), if/else 2, boolean chains 1 (nesting depth added 8). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
editorConfig.createEditorConfig (cognitive 18) gui/src/components/mainInput/TipTapEditor/utils/editorConfig.ts:79— editorConfig.createEditorConfig has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 306, 288, 327, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
UnifiedTerminal.UnifiedTerminalCommand (cognitive 18) REDACTED:338— UnifiedTerminal.UnifiedTerminalCommand has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, if/else 7, ternaries 2. Of this number, 14 points are the body's own statements and 4 belong to 3 function items inside it that branch. 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.
next-edit-4-2.updateEvent (cognitive 18) manual-testing-sandbox/next-edit/next-edit-4-2.ts:56— next-edit-4-2.updateEvent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GlobalContext.update (cognitive 17) core/util/GlobalContext.ts:63— GlobalContext.update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 3 (8 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MCPConnection.connectClient (cognitive 17) core/context/mcp/MCPConnection.ts:122— MCPConnection.connectClient has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, error handling 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
util.addModel (cognitive 17) core/config/util.ts:26— util.addModel has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 3, ternaries 3 (nesting depth added 2). None of this is in the body itself: all 17 points belong to 4 function literals inside it that branch (lines 31, 59, 61, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chat.llama2TemplateMessages (cognitive 17) core/llm/templates/chat.ts:53— chat.llama2TemplateMessages has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 1 (2 pts), boolean chains 1, 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.
countTokens.compileChatMessages (cognitive 17) core/llm/countTokens.ts:422— countTokens.compileChatMessages has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
charStream.stopAtStopTokens (cognitive 17) core/autocomplete/filtering/streamTransforms/charStream.ts:76— charStream.stopAtStopTokens has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 3 (8 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ChunkCodebaseIndex.update (cognitive 17) core/indexing/chunk/ChunkCodebaseIndex.ts:31— ChunkCodebaseIndex.update has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 4 (5 pts), error handling 2 (4 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.
CodeSnippetsCodebaseIndex.getSnippetsFromMatch (cognitive 17) core/indexing/CodeSnippetsIndex.ts:126— CodeSnippetsCodebaseIndex.getSnippetsFromMatch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (16 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.
fetchModels.fetchOllamaModels (cognitive 17) core/llm/fetchModels.ts:64— fetchModels.fetchOllamaModels has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 3 (5 pts), ternaries 2 (4 pts), error handling 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.
grepSearch.formatGrepSearchResults (cognitive 17) core/util/grepSearch.ts:8— grepSearch.formatGrepSearchResults has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 2 (nesting depth added 3). Of this number, 10 points are the body's own statements and 7 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
recursiveStream.recursiveStream (cognitive 17) core/edit/recursiveStream.ts:24— recursiveStream.recursiveStream has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 2 (4 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseLLM.parseError (cognitive 17) core/llm/index.ts:405— BaseLLM.parseError has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LLMLogFormatter.logMessage (cognitive 17) core/llm/logFormatter.ts:286— LLMLogFormatter.logMessage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, ternaries 1 (2 pts), 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.
SystemMessageToolCodeblocksFramework.toolToSystemToolDefinition (cognitive 17) core/tools/systemMessageTools/toolCodeblocks/index.ts:33— SystemMessageToolCodeblocksFramework.toolToSystemToolDefinition has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 1 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModelRecommendations.ModelRecommendations (cognitive 17) docs/snippets/ModelRecommendations.jsx:1— ModelRecommendations.ModelRecommendations has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 5). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (parseMarkdownLinks, a function literal at line 186). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ColoredDiff.ColoredDiff (cognitive 17) extensions/cli/src/ui/ColoredDiff.tsx:176— ColoredDiff.ColoredDiff has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, match/switch 1 (2 pts), loops 1 (nesting depth added 4). Of this number, 12 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileSearchUI.FileSearchUI (cognitive 17) extensions/cli/src/ui/FileSearchUI.tsx:58— FileSearchUI.FileSearchUI has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 4). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 78, 103, 72). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ChecklistDisplay.ChecklistDisplay (cognitive 17) extensions/cli/src/ui/components/ChecklistDisplay.tsx:11— ChecklistDisplay.ChecklistDisplay has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 5 (6 pts), boolean chains 1, loops 1 (nesting depth added 6). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 29). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
suggestions.selectSuggestion (cognitive 17) extensions/vscode/src/suggestions.ts:185— suggestions.selectSuggestion has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 2 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useMainEditorWebviewListeners.useMainEditorWebviewListeners (cognitive 17) gui/src/components/mainInput/TipTapEditor/useMainEditorWebviewListeners.ts:17— useMainEditorWebviewListeners.useMainEditorWebviewListeners has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 2, loops 2 (nesting depth added 2). None of this is in the body itself: all 17 points belong to 6 function literals inside it that branch (lines 113, 194, 204, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ModeSelect.ModeSelect (cognitive 17) gui/src/components/ModeSelect/ModeSelect.tsx:19— ModeSelect.ModeSelect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 5, ternaries 4 (5 pts) (nesting depth added 1). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 36, 64, 24, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
UnifiedTerminal.convertBundleIntoReact (cognitive 17) REDACTED:152— UnifiedTerminal.convertBundleIntoReact has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (10 pts), if/else 3 (4 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
UserSetting.UserSetting::renderControl (cognitive 17) gui/src/pages/config/components/UserSetting.tsx:64— UserSetting.UserSetting::renderControl has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (12 pts), boolean chains 2, if/else 1 (2 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.
useLLMLog.appendItemsToLLMLog (cognitive 17) gui/src/hooks/useLLMLog.ts:118— useLLMLog.appendItemsToLLMLog has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2, match/switch 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Message.renderMessage (cognitive 17) gui/src/components/console/Message.tsx:43— Message.renderMessage has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
TaskManager.createTask (cognitive 17) manual-testing-sandbox/next-edit/next-edit-10-5.ts:112— TaskManager.createTask has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 7 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WatsonXApi.completionStream (cognitive 17) packages/openai-adapters/src/apis/WatsonX.ts:252— WatsonXApi.completionStream has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 3 (4 pts), boolean chains 3, error handling 1 (3 pts), loops 1 (nesting depth added 5). Of this number, 11 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
evaluateTerminalCommandSecurity.extractSubstitutedCommands (cognitive 17) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:1122— evaluateTerminalCommandSecurity.extractSubstitutedCommands has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
lineStream.filterLeadingAndTrailingNewLineInsertion (cognitive 16) core/autocomplete/filtering/streamTransforms/lineStream.ts:559— lineStream.filterLeadingAndTrailingNewLineInsertion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GeneratorReuseManager.getGenerator (cognitive 16) core/autocomplete/generation/GeneratorReuseManager.ts:41— GeneratorReuseManager.getGenerator has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 3, loops 2 (3 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.
index.isExtremeRepetition (cognitive 16) core/autocomplete/postprocessing/index.ts:25— index.isExtremeRepetition has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (4 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.
NextEditProvider._handleCompletion (cognitive 16) core/nextEdit/NextEditProvider.ts:439— NextEditProvider._handleCompletion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
DocsCrawler.crawl (cognitive 16) core/indexing/docs/crawlers/DocsCrawler.ts:43— DocsCrawler.crawl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 1 (2 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
article.breakdownArticleComponent (cognitive 16) core/indexing/docs/article.ts:26— article.breakdownArticleComponent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
handlebarUtils.prepareTemplatedFilepaths (cognitive 16) REDACTED:34— handlebarUtils.prepareTemplatedFilepaths has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (2 pts), loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Anthropic.getContentBlocksFromChatMessage (cognitive 16) core/llm/llms/Anthropic.ts:146— Anthropic.getContentBlocksFromChatMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Ollama._streamFim (cognitive 16) core/llm/llms/Ollama.ts:657— Ollama._streamFim has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), error handling 1 (4 pts), loops 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.
WatsonX._streamComplete (cognitive 16) core/llm/llms/WatsonX.ts:194— WatsonX._streamComplete has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 4, error handling 1 (3 pts), loops 1 (nesting depth added 5). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 241, 252). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
AutocompleteTemplate.getTemplateForModel (cognitive 16) core/autocomplete/templating/AutocompleteTemplate.ts:517— AutocompleteTemplate.getTemplateForModel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, boolean chains 5. 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.
isAbortError.isAbortError (cognitive 16) core/util/isAbortError.ts:10— isAbortError.isAbortError has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocalPlatformClient.findSecretInWorkspaceEnvFiles (cognitive 16) core/config/yaml/LocalPlatformClient.ts:52— LocalPlatformClient.findSecretInWorkspaceEnvFiles has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 2 (5 pts), error handling 2 (3 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NextEditEditableRegionCalculator.compareAsts::traverse (cognitive 16) core/nextEdit/NextEditEditableRegionCalculator.ts:710— NextEditEditableRegionCalculator.compareAsts::traverse has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 2 (4 pts), if/else 3, loops 1 (nesting depth added 2). 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.
CLIPlatformClient.resolveFQSNs (cognitive 16) extensions/cli/src/CLIPlatformClient.ts:90— CLIPlatformClient.resolveFQSNs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (4 pts), loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 7). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
executor.executeSubAgent (cognitive 16) extensions/cli/src/subagent/executor.ts:58— executor.executeSubAgent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, boolean chains 5, ternaries 2, error handling 1. Of this number, 14 points are the body's own statements and 2 belong to 2 function literals inside it that branch. 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.
chat.processMessage (cognitive 16) extensions/cli/src/commands/chat.ts:342— chat.processMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (2 pts), boolean chains 1, error handling 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.
smoke-api-helpers.pollUntilIdle (cognitive 16) extensions/cli/src/smoke-api/smoke-api-helpers.ts:213— smoke-api-helpers.pollUntilIdle has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
debug.registerDebugTracker (cognitive 16) extensions/vscode/src/debug/debug.ts:9— debug.registerDebugTracker has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 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.
suggestions.rerenderDecorations (cognitive 16) extensions/vscode/src/suggestions.ts:57— suggestions.rerenderDecorations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, loops 2 (nesting depth added 4). Of this number, 12 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
callToolById.callToolById (cognitive 16) gui/src/redux/thunks/callToolById.ts:23— callToolById.callToolById has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 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.
renderPromptv2.getPromptV2ContextRequests (cognitive 16) gui/src/components/mainInput/TipTapEditor/utils/renderPromptv2.ts:7— renderPromptv2.getPromptV2ContextRequests has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (nesting depth added 8). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (addContextRequestsRecursive). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
RulesSection.RuleCard (cognitive 16) gui/src/pages/config/sections/RulesSection.tsx:135— RulesSection.RuleCard has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 7 (8 pts), boolean chains 5, if/else 2, error handling 1 (nesting depth added 1). Of this number, 11 points are the body's own statements and 5 belong to 4 function items inside it that branch. 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.
AnthropicUtils.addCacheControlToLastTwoUserMessages (cognitive 16) packages/openai-adapters/src/apis/AnthropicUtils.ts:99— AnthropicUtils.addCacheControlToLastTwoUserMessages has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IdeProtocolClient.handleMessage (cognitive 16) extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/IdeProtocolClient.kt:52— IdeProtocolClient.handleMessage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), error handling 1, match/switch 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.
Change coupling clique: ide.ts, messageIde.ts, filesystem.ts, VsCodeIde.ts core/protocol/ide.ts— 4 files — `core/protocol/ide.ts`, `core/protocol/messenger/messageIde.ts`, `core/util/filesystem.ts`, `extensions/vscode/src/VsCodeIde.ts` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change-coupling hub: core.ts → passThrough.ts, webview.ts, MessageTypes.kt core/core.ts— `core/core.ts` changes together with 3 other files — `core/protocol/passThrough.ts`, `core/protocol/webview.ts`, `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/constants/MessageTypes.kt` — 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.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) sync/src/lib.rs:46— sync/src/lib.rs:46-106 | sync/src/lib.rs:108-159 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (22 lines × 2) extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditJumpManager.kt:236— extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditJumpManager.kt:236-257 | extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditWindowManager.kt:192-213 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/ConfigJsonSchemaProviderFactory.kt:39— extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/ConfigJsonSchemaProviderFactory.kt:39-43 | extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/ConfigRcJsonSchemaProviderFactory.kt:39-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/ConfigJsonSchemaProviderFactory.kt:39` 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 (5 lines × 3) extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/activities/ContinuePluginStartupActivity.kt:205— extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/activities/ContinuePluginStartupActivity.kt:205-209 | extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/activities/ContinuePluginStartupActivity.kt:224-228 | extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/activities/ContinuePluginStartupActivity.kt:265-269 — 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 (13 lines × 2) sync/src/utils.rs:21— sync/src/utils.rs:21-33 | sync/src/utils/mod.rs:21-33 — 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.
End-of-life runtime: Node.js 20 .nvmrc:1— .nvmrc declares Node.js 20 as this project's version file, and Node.js 20, support ended 2026-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
Duplication concentrated across 7 sibling directories (51 clone groups) core/llm/llms/gemini-types.ts:1— 51 duplicated blocks under the repository root have copies in at least two of the sibling directories binary, core, docs-site, extensions, gui, packages (+1 more sibling(s) not listed) — 34 of them are reported below, and 17 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 51 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 51 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 51 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (9 clone groups) packages/config-types/src/index.ts:22— 9 duplicated blocks under packages/ have copies in at least two of the sibling directories config-types, config-yaml, openai-adapters — 4 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (7 clone groups) gui/src/context/MockIdeMessenger.ts:49— 7 duplicated blocks under gui/src/ have copies in at least two of the sibling directories components, context, hooks, pages, redux — 2 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (6 clone groups) core/autocomplete/CompletionProvider.ts:66— 6 duplicated blocks under core/ have copies in at least two of the sibling directories autocomplete, config, context, nextEdit, promptFiles — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 8 sibling directories (6 clone groups) packages/config-yaml/src/schemas/data/autocomplete/v0.1.0.ts:23— 6 duplicated blocks under packages/config-yaml/src/schemas/data/ have copies in at least two of the sibling directories autocomplete, chatFeedback, chatInteraction, editInteraction, editOutcome, nextEditOutcome (+2 more sibling(s) not listed) — 2 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (291 identical lines × 2 files) REDACTED:14— REDACTED:14 · REDACTED:14 — these 2 files are line-for-line copies of one another — 291 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Wholesale file copy (268 identical lines × 2 files) core/llm/llms/gemini-types.ts:1— core/llm/llms/gemini-types.ts:1 · packages/openai-adapters/src/util/gemini-types.ts:1 — these 2 files are line-for-line copies of one another — 268 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication· Duplicated block with local edits (156 matched lines × 2 locations) · ×1
Duplicated block with local edits (156 matched lines × 2 locations) manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts:5— manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts:5 · manual-testing-sandbox/next-edit/next-edit-6-3.ts:5 — the two spans are one implementation copied and then locally edited — 697 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (98 matched lines × 2 locations) · ×1
Duplicated block with local edits (98 matched lines × 2 locations) core/nextEdit/providers/InstinctNextEditProvider.ts:16— core/nextEdit/providers/InstinctNextEditProvider.ts:16 · core/nextEdit/providers/MercuryCoderNextEditProvider.ts:17 — the two spans are one implementation copied and then locally edited — 457 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (94 matched lines × 2 locations) · ×1
Duplicated block with local edits (94 matched lines × 2 locations) core/autocomplete/CompletionProvider.ts:66— core/autocomplete/CompletionProvider.ts:66 · core/nextEdit/NextEditProvider.ts:130 — the two spans are one implementation copied and then locally edited — 526 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (80 matched lines × 2 locations) · ×1
Duplicated block with local edits (80 matched lines × 2 locations) extensions/vscode/scripts/prepackage.js:193— extensions/vscode/scripts/prepackage.js:193 · extensions/vscode/scripts/utils.js:117 — the two spans are one implementation copied and then locally edited — 403 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (64 matched lines × 2 locations) · ×1
Duplicated block with local edits (64 matched lines × 2 locations) extensions/cli/src/ui/components/ChatScreenContent.tsx:14— extensions/cli/src/ui/components/ChatScreenContent.tsx:14 · extensions/cli/src/ui/components/ScreenContent.tsx:32 — the two spans are one implementation copied and then locally edited — 269 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (62 matched lines × 2 locations) · ×1
Duplicated block with local edits (62 matched lines × 2 locations) core/llm/llms/Anthropic.ts:132— core/llm/llms/Anthropic.ts:132 · packages/openai-adapters/src/apis/Anthropic.ts:163 — the two spans are one implementation copied and then locally edited — 295 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (60 lines × 2 locations) core/context/retrieval/pipelines/NoRerankerRetrievalPipeline.ts:19— core/context/retrieval/pipelines/NoRerankerRetrievalPipeline.ts:19 · core/context/retrieval/pipelines/RerankerRetrievalPipeline.ts:16 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (54 matched lines × 2 locations) · ×1
Duplicated block with local edits (54 matched lines × 2 locations) core/llm/llms/Inception.ts:70— core/llm/llms/Inception.ts:70 · packages/openai-adapters/src/apis/Inception.ts:109 — the two spans are one implementation copied and then locally edited — 319 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (53 lines × 2 locations) binary/src/IpcMessenger.ts:29— binary/src/IpcMessenger.ts:29 · binary/src/TcpMessenger.ts:65 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (50 matched lines × 2 locations) · ×1
Duplicated block with local edits (50 matched lines × 2 locations) packages/config-types/src/index.ts:22— packages/config-types/src/index.ts:22 · packages/config-yaml/src/schemas/models.ts:3 — the two spans are one implementation copied and then locally edited — 480 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (47 matched lines × 2 locations) · ×1
Duplicated block with local edits (47 matched lines × 2 locations) core/autocomplete/util/AutocompleteLoggingService.ts:41— core/autocomplete/util/AutocompleteLoggingService.ts:41 · core/nextEdit/NextEditLoggingService.ts:112 — the two spans are one implementation copied and then locally edited — 319 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (45 matched lines × 2 locations) · ×1
Duplicated block with local edits (45 matched lines × 2 locations) core/autocomplete/templating/AutocompleteTemplate.ts:179— core/autocomplete/templating/AutocompleteTemplate.ts:179 · core/autocomplete/templating/AutocompleteTemplate.ts:237 — the two spans are one implementation copied and then locally edited — 242 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (43 matched lines × 2 locations) · ×1
Duplicated block with local edits (43 matched lines × 2 locations) core/llm/llms/Bedrock.ts:467— core/llm/llms/Bedrock.ts:467 · packages/openai-adapters/src/apis/Bedrock.ts:282 — the two spans are one implementation copied and then locally edited — 212 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (43 lines × 2 locations) packages/openai-adapters/src/apis/AiSdk.ts:101— packages/openai-adapters/src/apis/AiSdk.ts:101 · packages/openai-adapters/src/apis/AiSdk.ts:186 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (42 lines × 2 locations) core/llm/templates/edit/codestral.ts:4— core/llm/templates/edit/codestral.ts:4 · core/llm/templates/edit/gpt.ts:4 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (39 lines × 3 locations) core/llm/index.ts:656— core/llm/index.ts:656 · core/llm/index.ts:786 · core/llm/index.ts:894 — 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.
R10 · Code Duplication· Duplicated block with local edits (37 matched lines × 2 locations) · ×1
Duplicated block with local edits (37 matched lines × 2 locations) REDACTED:35— REDACTED:35 · REDACTED:97 — the two spans are one implementation copied and then locally edited — 249 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (36 lines × 2 locations) packages/openai-adapters/src/apis/OpenRouterCaching.ts:181— packages/openai-adapters/src/apis/OpenRouterCaching.ts:181 · packages/openai-adapters/src/apis/OpenRouterCaching.ts:239 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (35 lines × 2 locations) core/llm/llms/SageMaker.ts:39— core/llm/llms/SageMaker.ts:39 · core/llm/llms/SageMaker.ts:87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (33 matched lines × 2 locations) · ×1
Duplicated block with local edits (33 matched lines × 2 locations) extensions/cli/src/ui/ConfigSelector.tsx:24— extensions/cli/src/ui/ConfigSelector.tsx:24 · extensions/cli/src/ui/ModelSelector.tsx:17 — the two spans are one implementation copied and then locally edited — 204 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (32 lines × 2 locations) core/llm/llms/Deepseek.ts:26— core/llm/llms/Deepseek.ts:26 · core/llm/llms/LlamaStack.ts:23 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (32 matched lines × 2 locations) · ×1
Duplicated block with local edits (32 matched lines × 2 locations) core/llm/llms/Docker.ts:171— core/llm/llms/Docker.ts:171 · core/llm/llms/Ollama.ts:770 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Complex function provideInlineCompletionItems (cyclomatic 60, cognitive 92) extensions/vscode/src/autocomplete/completionProvider.ts:150— provideInlineCompletionItems has cyclomatic complexity 60 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function constructLlmApi (cyclomatic 55, cognitive 12) packages/openai-adapters/src/index.ts:84— constructLlmApi has cyclomatic complexity 55 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 44, cognitive 63) gui/src/redux/thunks/streamNormalInput.ts:81— (anonymous) has cyclomatic complexity 44 and cognitive complexity 63; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function streamUpdate (cyclomatic 35, cognitive 67) REDACTED:524— streamUpdate has cyclomatic complexity 35 and cognitive complexity 67; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleResponsesFinal (cyclomatic 34, cognitive 87) core/llm/openaiTypeConverters.ts:622— handleResponsesFinal has cyclomatic complexity 34 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function analyzeError (cyclomatic 34, cognitive 49) gui/src/util/errorAnalysis.ts:38— analyzeError has cyclomatic complexity 34 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 33, cognitive 46) packages/fetch/src/node-fetch-patch.js:171— (anonymous) has cyclomatic complexity 33 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function convertVercelStreamPart (cyclomatic 32, cognitive 24) packages/openai-adapters/src/vercelStreamConverter.ts:83— convertVercelStreamPart has cyclomatic complexity 32 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function postprocessCompletion (cyclomatic 31, cognitive 39) core/autocomplete/postprocessing/index.ts:92— postprocessCompletion has cyclomatic complexity 31 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function streamChat (cyclomatic 30, cognitive 66) core/llm/index.ts:1095— streamChat has cyclomatic complexity 30 and cognitive complexity 66; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _convertMessages (cyclomatic 29, cognitive 77) core/llm/llms/Bedrock.ts:362— _convertMessages has cyclomatic complexity 29 and cognitive complexity 77; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 29, cognitive 60) core/llm/llms/OpenAI.ts:62— (anonymous) has cyclomatic complexity 29 and cognitive complexity 60; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function migrateJsonSharedConfig (cyclomatic 29, cognitive 54) core/config/migrateSharedConfig.ts:18— migrateJsonSharedConfig has cyclomatic complexity 29 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function constructor (cyclomatic 29, cognitive 41) core/llm/llms/VertexAI.ts:61— constructor has cyclomatic complexity 29 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fetchwithRequestOptions (cyclomatic 29, cognitive 36) packages/fetch/src/fetch.ts:82— fetchwithRequestOptions has cyclomatic complexity 29 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isCriticalCommand (cyclomatic 29, cognitive 34) packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:402— isCriticalCommand has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function searchFiles (cyclomatic 28, cognitive 47) manual-testing-sandbox/next-edit/next-edit-6-3.ts:232— searchFiles has cyclomatic complexity 28 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function autodetectTemplateType (cyclomatic 28, cognitive 27) core/llm/autodetect.ts:313— autodetectTemplateType has cyclomatic complexity 28 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function defaultShouldRetry (cyclomatic 28, cognitive 25) core/llm/utils/retry.ts:42— defaultShouldRetry has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fromResponsesChunk (cyclomatic 28, cognitive 25) packages/openai-adapters/src/apis/openaiResponses.ts:575— fromResponsesChunk has cyclomatic complexity 28 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 1375 lines of code REDACTED:1— REDACTED has 1375 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/llm/index.ts: 1351 lines of code core/llm/index.ts:1— core/llm/index.ts has 1351 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/core.ts: 1295 lines of code core/core.ts:1— core/core.ts has 1295 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/terminal-security/src/evaluateTerminalCommandSecurity.ts · ×1
packages/terminal-security/src/evaluateTerminalCommandSecurity.ts: 1110 lines of code packages/terminal-security/src/evaluateTerminalCommandSecurity.ts:1— packages/terminal-security/src/evaluateTerminalCommandSecurity.ts has 1110 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/autocomplete/filtering/streamTransforms/lineStream.vitest.ts · ×1
core/autocomplete/filtering/streamTransforms/lineStream.vitest.ts: 1099 lines of code core/autocomplete/filtering/streamTransforms/lineStream.vitest.ts:1— core/autocomplete/filtering/streamTransforms/lineStream.vitest.ts has 1099 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/config/types.ts: 1095 lines of code core/config/types.ts:1— core/config/types.ts has 1095 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/llm/openaiTypeConverters.ts · ×1
core/llm/openaiTypeConverters.ts: 1041 lines of code core/llm/openaiTypeConverters.ts:1— core/llm/openaiTypeConverters.ts has 1041 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1030 lines of code REDACTED:1— REDACTED has 1030 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts · ×1
manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts: 910 lines of code manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:1— manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts has 910 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/activation/NextEditWindowManager.ts · ×1
extensions/vscode/src/activation/NextEditWindowManager.ts: 900 lines of code extensions/vscode/src/activation/NextEditWindowManager.ts:1— extensions/vscode/src/activation/NextEditWindowManager.ts has 900 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/commands.ts · ×1
extensions/vscode/src/commands.ts: 836 lines of code extensions/vscode/src/commands.ts:1— extensions/vscode/src/commands.ts has 836 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/config/load.ts: 833 lines of code core/config/load.ts:1— core/config/load.ts has 833 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/cli/src/ui/UserInput.tsx · ×1
extensions/cli/src/ui/UserInput.tsx: 804 lines of code extensions/cli/src/ui/UserInput.tsx:1— extensions/cli/src/ui/UserInput.tsx has 804 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/activation/NextEditWindowManager.vitest.ts · ×1
extensions/vscode/src/activation/NextEditWindowManager.vitest.ts: 803 lines of code extensions/vscode/src/activation/NextEditWindowManager.vitest.ts:1— extensions/vscode/src/activation/NextEditWindowManager.vitest.ts has 803 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/llm/llms/Cohere.vitest.ts · ×1
core/llm/llms/Cohere.vitest.ts: 801 lines of code core/llm/llms/Cohere.vitest.ts:1— core/llm/llms/Cohere.vitest.ts has 801 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/nextEdit/NextEditEditableRegionCalculator.ts · ×1
core/nextEdit/NextEditEditableRegionCalculator.ts: 784 lines of code core/nextEdit/NextEditEditableRegionCalculator.ts:1— core/nextEdit/NextEditEditableRegionCalculator.ts has 784 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/indexing/CodebaseIndexer.ts · ×1
core/indexing/CodebaseIndexer.ts: 781 lines of code core/indexing/CodebaseIndexer.ts:1— core/indexing/CodebaseIndexer.ts has 781 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/autocomplete/context/static-context/StaticContextService.ts · ×1
core/autocomplete/context/static-context/StaticContextService.ts: 777 lines of code core/autocomplete/context/static-context/StaticContextService.ts:1— core/autocomplete/context/static-context/StaticContextService.ts has 777 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/cli/src/ui/hooks/useChat.ts · ×1
extensions/cli/src/ui/hooks/useChat.ts: 774 lines of code extensions/cli/src/ui/hooks/useChat.ts:1— extensions/cli/src/ui/hooks/useChat.ts has 774 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/activation/SelectionChangeManager.vitest.ts · ×1
extensions/vscode/src/activation/SelectionChangeManager.vitest.ts: 768 lines of code extensions/vscode/src/activation/SelectionChangeManager.vitest.ts:1— extensions/vscode/src/activation/SelectionChangeManager.vitest.ts has 768 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/llm/llms/Ollama.ts: 752 lines of code core/llm/llms/Ollama.ts:1— core/llm/llms/Ollama.ts has 752 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/openai-adapters/src/apis/openaiResponses.ts · ×1
packages/openai-adapters/src/apis/openaiResponses.ts: 722 lines of code packages/openai-adapters/src/apis/openaiResponses.ts:1— packages/openai-adapters/src/apis/openaiResponses.ts has 722 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/tools/implementations/runTerminalCommand.vitest.ts · ×1
core/tools/implementations/runTerminalCommand.vitest.ts: 718 lines of code core/tools/implementations/runTerminalCommand.vitest.ts:1— core/tools/implementations/runTerminalCommand.vitest.ts has 718 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/llm/llms/Bedrock.ts: 691 lines of code core/llm/llms/Bedrock.ts:1— core/llm/llms/Bedrock.ts has 691 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/openai-adapters/src/apis/Bedrock.ts · ×1
packages/openai-adapters/src/apis/Bedrock.ts: 658 lines of code packages/openai-adapters/src/apis/Bedrock.ts:1— packages/openai-adapters/src/apis/Bedrock.ts has 658 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/llm/llms/OpenAI.ts: 655 lines of code core/llm/llms/OpenAI.ts:1— core/llm/llms/OpenAI.ts has 655 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/autocomplete/completionProvider.ts · ×1
extensions/vscode/src/autocomplete/completionProvider.ts: 633 lines of code extensions/vscode/src/autocomplete/completionProvider.ts:1— extensions/vscode/src/autocomplete/completionProvider.ts has 633 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/VsCodeIde.ts · ×1
extensions/vscode/src/VsCodeIde.ts: 617 lines of code extensions/vscode/src/VsCodeIde.ts:1— extensions/vscode/src/VsCodeIde.ts has 617 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
core/diff/myers.vitest.ts: 614 lines of code core/diff/myers.vitest.ts:1— core/diff/myers.vitest.ts has 614 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/autocomplete/filtering/streamTransforms/lineStream.ts · ×1
core/autocomplete/filtering/streamTransforms/lineStream.ts: 600 lines of code core/autocomplete/filtering/streamTransforms/lineStream.ts:1— core/autocomplete/filtering/streamTransforms/lineStream.ts has 600 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/cli/src/stream/streamChatResponse.helpers.ts · ×1
extensions/cli/src/stream/streamChatResponse.helpers.ts: 574 lines of code extensions/cli/src/stream/streamChatResponse.helpers.ts:1— extensions/cli/src/stream/streamChatResponse.helpers.ts has 574 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· core/context/mcp/MCPConnection.ts · ×1
core/context/mcp/MCPConnection.ts: 567 lines of code core/context/mcp/MCPConnection.ts:1— core/context/mcp/MCPConnection.ts has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/util/ideUtils.ts · ×1
extensions/vscode/src/util/ideUtils.ts: 567 lines of code extensions/vscode/src/util/ideUtils.ts:1— extensions/vscode/src/util/ideUtils.ts has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts · ×1
manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts: 567 lines of code manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts:1— manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/diff/vertical/handler.ts · ×1
extensions/vscode/src/diff/vertical/handler.ts: 566 lines of code extensions/vscode/src/diff/vertical/handler.ts:1— extensions/vscode/src/diff/vertical/handler.ts has 566 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/cli/src/commands/chat.ts · ×1
extensions/cli/src/commands/chat.ts: 564 lines of code extensions/cli/src/commands/chat.ts:1— extensions/cli/src/commands/chat.ts has 564 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 563 lines of code REDACTED:1— REDACTED has 563 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· gui/src/components/mainInput/AtMentionDropdown/index.tsx · ×1
gui/src/components/mainInput/AtMentionDropdown/index.tsx: 561 lines of code gui/src/components/mainInput/AtMentionDropdown/index.tsx:1— gui/src/components/mainInput/AtMentionDropdown/index.tsx has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· gui/src/context/SubmenuContextProviders.tsx · ×1
gui/src/context/SubmenuContextProviders.tsx: 556 lines of code gui/src/context/SubmenuContextProviders.tsx:1— gui/src/context/SubmenuContextProviders.tsx has 556 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· extensions/vscode/src/diff/vertical/manager.ts · ×1
extensions/vscode/src/diff/vertical/manager.ts: 550 lines of code extensions/vscode/src/diff/vertical/manager.ts:1— extensions/vscode/src/diff/vertical/manager.ts has 550 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~983 LoC) manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~911 LoC) core/nextEdit/NextEditEditableRegionCalculator.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~582 LoC) manual-testing-sandbox/next-edit/next-edit-8-4-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~562 LoC) manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~504 LoC) manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~445 LoC) core/codeRenderer/CodeRenderer.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~440 LoC) manual-testing-sandbox/next-edit/next-edit-10-5.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~409 LoC) REDACTED— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~406 LoC) manual-testing-sandbox/next-edit/next-edit-6-3.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~381 LoC) manual-testing-sandbox/next-edit/next-edit-7-4-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~315 LoC) manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~297 LoC) manual-testing-sandbox/next-edit/next-edit-9-5.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~262 LoC) manual-testing-sandbox/next-edit/next-edit-5-3.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~256 LoC) gui/src/components/modelSelection/ModelCard.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~236 LoC) manual-testing-sandbox/next-edit/next-edit-4-2-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~231 LoC) extensions/cli/src/hooks/fireHook.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~230 LoC) core/protocol/messenger/messageIde.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~211 LoC) manual-testing-sandbox/next-edit/next-edit-7-4.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~210 LoC) gui/src/components/AssistantAndOrgListbox/shared.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~172 LoC) core/protocol/messenger/reverseMessageIde.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~167 LoC) docs-site/components/ui/command.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~161 LoC) manual-testing-sandbox/next-edit/next-edit-4-2.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~157 LoC) gui/src/pages/config/features/keyboard/KeyboardShortcuts.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~123 LoC) docs-site/components/ui/dialog.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (docs-site/components/ui/command.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~119 LoC) extensions/cli/src/ui/ServiceDebugger.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~114 LoC) manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~111 LoC) manual-testing-sandbox/next-edit/next-edit-3-2.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~110 LoC) gui/src/components/indexing/ChatIndexingPeeks.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~109 LoC) core/protocol/passThrough.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~107 LoC) manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~103 LoC) extensions/cli/src/fileTools.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~94 LoC) actions/general-review/scripts/buildPrompt.js— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~93 LoC) core/llm/llms/llmTestHarness.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~83 LoC) extensions/cli/src/ui/components/ToolPermissionRequest.tsx— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~81 LoC) core/tools/systemMessageTools/convertSystemTools.ts— no import path from any entry point (97 application, 44 tooling, 504 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unlisted import 'web-tree-sitter' extensions/vscode/src/autocomplete/lsp.ts:24— Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json.
Unused dependency '@biomejs/biome' — Declared in binary/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@vercel/ncc' — Declared in binary/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'follow-redirects' — Declared in binary/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Orphaned file extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditJumpManager.kt: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 manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts: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 packages/fetch/src/node-fetch-patch.js: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 packages/openai-adapters/src/apis/VertexAI.ts: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 extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditService.kt: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 manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts: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 manual-testing-sandbox/next-edit/next-edit-10-5.ts: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 core/codeRenderer/CodeRenderer.ts: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 extensions/vscode/src/activation/JumpManager.ts: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 core/nextEdit/providers/BaseNextEditProvider.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file core/nextEdit/diff/diff.ts: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 manual-testing-sandbox/next-edit/next-edit-7-4-sol.ts: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 core/llm/logFormatter.ts: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 extensions/vscode/src/activation/InlineTipManager.ts: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 extensions/vscode/src/activation/SelectionChangeManager.ts: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 extensions/cli/src/services/ServiceContainer.ts: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 manual-testing-sandbox/next-edit/next-edit-5-3-sol.ts: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 gui/src/components/svg/OllamaLogo.tsx: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 extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/listeners/SelectionChangeManager.kt: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 core/nextEdit/constants.ts: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 extensions/cli/src/ui/EditMessageSelector.tsx: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 core/llm/llms/SageMaker.ts: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 manual-testing-sandbox/next-edit/next-edit-6-3.ts: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 gui/src/pages/config/components/UserSetting.tsx: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.
Mock-dominated test: should handle edit mode apply state updates gui/src/redux/thunks/handleApplyStateUpdate.test.ts:92— This test sets up 4 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should exit edit mode when status is closed gui/src/redux/thunks/handleApplyStateUpdate.test.ts:110— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle non-edit mode apply state updates gui/src/redux/thunks/handleApplyStateUpdate.test.ts:147— This test sets up 4 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle accepted tool call closure gui/src/redux/thunks/handleApplyStateUpdate.test.ts:167— This test sets up 7 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle canceled tool call closure gui/src/redux/thunks/handleApplyStateUpdate.test.ts:219— This test sets up 7 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle errored tool call closure gui/src/redux/thunks/handleApplyStateUpdate.test.ts:267— This test sets up 6 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle closure when no tool call found gui/src/redux/thunks/handleApplyStateUpdate.test.ts:303— This test sets up 6 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle closure when no apply state found gui/src/redux/thunks/handleApplyStateUpdate.test.ts:330— This test sets up 6 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle apply state without toolCallId gui/src/redux/thunks/handleApplyStateUpdate.test.ts:367— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle different status values gui/src/redux/thunks/handleApplyStateUpdate.test.ts:383— This test sets up 4 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should successfully apply changes to file gui/src/redux/thunks/handleApplyStateUpdate.test.ts:428— This test sets up 4 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle IDE messenger request failure gui/src/redux/thunks/handleApplyStateUpdate.test.ts:458— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle IDE messenger error response gui/src/redux/thunks/handleApplyStateUpdate.test.ts:505— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not error if tool call is not in calling state gui/src/redux/thunks/handleApplyStateUpdate.test.ts:550— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not error if apply state is closed gui/src/redux/thunks/handleApplyStateUpdate.test.ts:584— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not error if tool call state is not found gui/src/redux/thunks/handleApplyStateUpdate.test.ts:618— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not error if apply state is not found gui/src/redux/thunks/handleApplyStateUpdate.test.ts:645— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle different payload types gui/src/redux/thunks/handleApplyStateUpdate.test.ts:670— This test sets up 4 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should dispose decorations on disposal extensions/vscode/src/activation/NextEditWindowManager.vitest.ts:910— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle errors in handlers gracefully extensions/vscode/src/activation/SelectionChangeManager.vitest.ts:550— This test sets up 3 test doubles (for example `vi
.fn`) against 1 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should prefetch editable regions when not using full file diff extensions/vscode/src/activation/SelectionChangeManager.vitest.ts:760— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should skip prefetching when using full file diff extensions/vscode/src/activation/SelectionChangeManager.vitest.ts:823— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should execute handlers in priority order and stop on first true return extensions/vscode/src/activation/SelectionChangeManager.vitest.ts:858— This test sets up 6 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should handle callbacks correctly extensions/cli/src/compaction.test.ts:374— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should call onClear callback when processing clear command extensions/cli/src/ui/hooks/useChat.clear.test.ts:28— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
+ 20 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-1-1-sol.ts:42— `manual-testing-sandbox/next-edit/next-edit-1-1-sol.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-1-1.ts:29— `manual-testing-sandbox/next-edit/next-edit-1-1.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:455— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 455 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:462— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 462 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:469— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 469 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:483— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 483 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:953— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 953 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:963— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 963 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:970— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 970 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:978— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 978 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:980— `manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts` reports through `console.*` at line 980 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5.ts:28— `manual-testing-sandbox/next-edit/next-edit-10-5.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5.ts:40— `manual-testing-sandbox/next-edit/next-edit-10-5.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5.ts:89— `manual-testing-sandbox/next-edit/next-edit-10-5.ts` reports through `console.*` at line 89 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-10-5.ts:154— `manual-testing-sandbox/next-edit/next-edit-10-5.ts` reports through `console.*` at line 154 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts:95— `manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts` reports through `console.*` at line 95 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts:97— `manual-testing-sandbox/next-edit/next-edit-2-1-sol.ts` reports through `console.*` at line 97 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-2-1.ts:53— `manual-testing-sandbox/next-edit/next-edit-2-1.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-2-1.ts:55— `manual-testing-sandbox/next-edit/next-edit-2-1.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts:109— `manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts` reports through `console.*` at line 109 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts:110— `manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts:111— `manual-testing-sandbox/next-edit/next-edit-3-2-sol.ts` reports through `console.*` at line 111 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-3-2.ts:98— `manual-testing-sandbox/next-edit/next-edit-3-2.ts` reports through `console.*` at line 98 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-3-2.ts:99— `manual-testing-sandbox/next-edit/next-edit-3-2.ts` reports through `console.*` at line 99 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel manual-testing-sandbox/next-edit/next-edit-3-2.ts:100— `manual-testing-sandbox/next-edit/next-edit-3-2.ts` reports through `console.*` at line 100 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Duplicated predicate extensions/cli/src/ui/hooks/useChat.helpers.ts:294— `!diffContent || diffContent.trim() === ""` appears character-identically in 3 files — extensions/cli/src/ui/hooks/useChat.helpers.ts, extensions/cli/src/ui/hooks/useChat.remote.helpers.ts, extensions/cli/src/util/metadata.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/llm/llms/gemini-types.ts:70— `!jsonSchemaType || typeof jsonSchema.type !== "string"` appears character-identically in 2 files — core/llm/llms/gemini-types.ts, packages/openai-adapters/src/util/gemini-types.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:323— `!matchesTitle && !matchesDescription && !matchesTags` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-10-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/llm/llms/Asksage.ts:107— `!this.sessionTokenPromise || Date.now() - this.tokenTimestamp > TOKEN_TTL` appears character-identically in 2 files — core/llm/llms/Asksage.ts, packages/openai-adapters/src/apis/AskSage.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate gui/src/components/mainInput/InputToolbar.tsx:257— `a.hideAddContext === b.hideAddContext && a.hideImageUpload === b.hideImageUpload && a.hideUseCodebase === b.hideUseCodebase && a.hideSelectM…` appears character-identically in 2 files — gui/src/components/mainInput/InputToolbar.tsx, gui/src/components/mainInput/TipTapEditor/TipTapEditor.tsx. 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 manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:308— `criteria.assignedTo && task.assignedTo !== criteria.assignedTo` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-10-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:307— `criteria.priority && task.priority !== criteria.priority` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-10-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:310— `criteria.projectId && task.projectId !== criteria.projectId` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-10-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts:306— `criteria.status && task.status !== criteria.status` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-10-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-10-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/llm/llms/Asksage.ts:310— `data.text || data.answer || data.message || data.choices?.[0]?.message?.content || ""` appears character-identically in 2 files — core/llm/llms/Asksage.ts, packages/openai-adapters/src/apis/AskSage.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/llm/llms/Asksage.ts:388— `data.tool_calls || data.choices?.[0]?.message?.tool_calls` appears character-identically in 2 files — core/llm/llms/Asksage.ts, packages/openai-adapters/src/apis/AskSage.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate extensions/cli/src/version.ts:51— `error instanceof Error && error.name === "AbortError"` appears character-identically in 2 files — extensions/cli/src/version.ts, packages/fetch/src/fetch.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate extensions/cli/src/util/formatError.ts:39— `error.errors && Array.isArray(error.errors)` appears character-identically in 2 files — extensions/cli/src/util/formatError.ts, packages/config-yaml/src/load/unroll.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/llm/countTokens.ts:159— `fieldDesc && typeof fieldDesc === "string"` appears character-identically in 2 files — core/llm/countTokens.ts, extensions/cli/src/util/tokenizer.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/llm/countTokens.ts:155— `fieldType && typeof fieldType === "string"` appears character-identically in 2 files — core/llm/countTokens.ts, extensions/cli/src/util/tokenizer.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts:379— `filters.category && product.category !== filters.category` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-9-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts:387— `filters.maxPrice && product.price > filters.maxPrice` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-9-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts:383— `filters.minPrice && product.price < filters.minPrice` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-9-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts:391— `filters.status && product.status !== filters.status` appears character-identically in 2 files — manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-9-5.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate core/llm/llms/Bedrock.ts:566— `format === ImageFormat.JPEG || format === ImageFormat.PNG || format === ImageFormat.WEBP || format === ImageFormat.GIF` appears character-identically in 2 files — core/llm/llms/Bedrock.ts, packages/openai-adapters/src/apis/Bedrock.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate extensions/cli/src/tools/index.tsx:58— `idIndex !== -1 && idIndex + 1 < args.length` appears character-identically in 5 files — extensions/cli/src/tools/index.tsx, extensions/cli/src/tools/reportFailure.ts, extensions/cli/src/tools/status.ts, extensions/cli/src/tools/uploadArtifact.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate extensions/cli/src/services/ChatHistoryService.ts:306— `item.message.role === "assistant" && item.toolCallStates` appears character-identically in 2 files — extensions/cli/src/services/ChatHistoryService.ts, extensions/cli/src/stream/handleToolCalls.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:292— `item.message.role === "tool" || item.message.role === "user"` appears character-identically in 2 files — REDACTED, gui/src/redux/util/constructMessages.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate gui/src/redux/util/constructMessages.ts:161— `item.toolCallStates && item.toolCallStates.length > 0` appears character-identically in 2 files — gui/src/redux/util/constructMessages.ts, gui/src/redux/util/index.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:289— `item.uri?.type === "file" && item.uri?.value` appears character-identically in 2 files — REDACTED, gui/src/redux/thunks/updateFileSymbols.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Silent fallback default in catch extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/IntelliJIde.kt:584— `getBranch` swallows every exception into `"NONE"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. 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 in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch core/tools/parseArgs.ts:19— `safeParseToolCallArgs` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch extensions/cli/src/services/ResourceMonitoringService.ts:296— `getProcessUptime` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch extensions/cli/src/services/ResourceMonitoringService.ts:304— `getFreeMemory` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch extensions/cli/src/systemMessage.ts:38— `getGitStatus` swallows every exception into `return "Git status not available"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch extensions/cli/src/util/loadMarkdownSkills.ts:65— `getSkillFilesFromDir` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:92— `captureWorktreeDiff` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch extensions/cli/src/commands/review/reviewWorker.ts:92— `loadLocalAgentInstructions` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch extensions/vscode/src/util/ideUtils.ts:599— `getBranch` swallows every exception into `return "NONE"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch extensions/vscode/src/VsCodeIde.ts:406— `readFile` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
README/code drift docs/guides/github-mcp-continue-cookbook.mdx:24— docs/guides/github-mcp-continue-cookbook.mdx names Node.js 22, but the repository declares engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, pinned 20. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/guides/netlify-mcp-continuous-deployment.mdx:46— docs/guides/netlify-mcp-continuous-deployment.mdx names Node.js 22, but the repository declares engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, engines `>=20.20.1`, pinned 20. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift extensions/vscode/README.md:30— extensions/vscode/README.md links to `docs/images/agent.gif`, but `extensions/vscode/docs/images/agent.gif` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift extensions/vscode/README.md:36— extensions/vscode/README.md links to `docs/images/chat.gif`, but `extensions/vscode/docs/images/chat.gif` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift extensions/vscode/README.md:42— extensions/vscode/README.md links to `docs/images/edit.gif`, but `extensions/vscode/docs/images/edit.gif` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift extensions/vscode/README.md:48— extensions/vscode/README.md links to `docs/images/autocomplete.gif`, but `extensions/vscode/docs/images/autocomplete.gif` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 16 significant file(s) lose their only recent owner: extensions/vscode/src/activation/NextEditWindowManager.ts, extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditWindowManager.kt, core/nextEdit/NextEditEditableRegionCalculator.ts, extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditJumpManager.kt, extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditService.kt, core/codeRenderer/CodeRenderer.ts, extensions/vscode/src/activation/JumpManager.ts, core/nextEdit/diff/diff.ts (+8 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 14 significant file(s) lose their only recent owner: extensions/cli/src/services/StorageSyncService.ts, extensions/cli/src/commands/review.ts, core/llm/llms/test-utils/openai-test-utils.ts, packages/openai-adapters/src/apis/WatsonX.ts, REDACTED, extensions/cli/src/ui/hooks/useChat.remote.helpers.ts, extensions/cli/src/smoke-api/smoke-api-helpers.ts, extensions/cli/src/commands/review/reviewWorker.ts (+6 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 12 significant file(s) lose their only recent owner: gui/src/pages/gui/ToolCallDiv/MCPAppRenderer.tsx, gui/src/styles/ThemePage.tsx, packages/config-yaml/src/markdown/agentFiles.ts, gui/src/components/OSRContextMenu.tsx, extensions/cli/src/util/truncateOutput.ts, core/context/mcp/json/loadJsonMcpConfigs.ts, extensions/cli/src/tools/edit.ts, core/tools/definitions/multiEdit.ts (+4 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 10 significant file(s) lose their only recent owner: packages/openai-adapters/src/apis/AiSdk.ts, REDACTED, core/util/conversationCompaction.ts, extensions/cli/src/util/loadMarkdownSkills.ts, extensions/cli/src/ui/components/QuizPrompt.tsx, extensions/cli/src/tools/skills.ts, core/config/markdown/loadMarkdownSkills.ts, extensions/cli/src/tools/subagent.ts (+2 more). Pair on, review, or document these before any departure.
Fat interface: DefaultApiInterface (16 required operations) packages/continue-sdk/typescript/api/src/apis/DefaultApi.ts:87— `DefaultApiInterface` declares 16 required operations: `getAssistantRaw`, `getAssistant`, `getFreeTrialStatusRaw`, `getFreeTrialStatus`, `getModelsAddOnCheckoutUrlRaw`, `getModelsAddOnCheckoutUrl`, `getPolicyRaw`, `getPolicy`, `listAssistantFullSlugsRaw`, `listAssistantFullSlugs`, `listAssistantsRaw`, `listAssistants`, `listOrganizationsRaw`, `listOrganizations`, `syncSecretsRaw`, `syncSecrets`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 6 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 (62 single-owned of 630 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; 630 of the 1365 production source files in this repository met that bar). They are anonymized user #5 (3 file(s)), anonymized user #6 (2 file(s)), anonymized user #7 (2 file(s)), anonymized user #8 (1 file(s)), anonymized user #9 (1 file(s)), anonymized user #10 (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: gui/src/pages/config/sections/IndexingSettingsSection.tsx, gui/src/pages/config/configTabs.tsx, gui/src/components/mainInput/TipTapEditor/MainEditorProvider.tsx, extensions/cli/src/ui/EditMessageSelector.tsx, gui/src/components/StyledMarkdownPreview/SecureImageComponent.tsx, extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/continue/process/ContinueBinaryProcess.kt, extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/license/AddLicenseKey.kt, packages/openai-adapters/src/apis/AskSage.ts (+2 more).
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
REDACTED
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 107 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditJumpManager.kt, manual-testing-sandbox/next-edit/next-edit-6-3-sol.ts, packages/fetch/src/node-fetch-patch.js, packages/openai-adapters/src/apis/VertexAI.ts, extensions/intellij/src/main/kotlin/com/github/continuedev/continueintellijextension/nextEdit/NextEditService.kt, manual-testing-sandbox/next-edit/next-edit-9-5-sol.ts, manual-testing-sandbox/next-edit/next-edit-10-5.ts, core/codeRenderer/CodeRenderer.ts (and 99 more) (114 orphaned of 633 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; 633 of the 1365 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.
DM9 · Scattered domain decisions· Rule about [enterText, hideAddContext, hideImageUpload, hideSelectModel, hideUseCodebase] decided in 2 places · ×1
Rule about [enterText, hideAddContext, hideImageUpload, hideSelectModel, hideUseCodebase] decided in 2 places — gui.src.components.mainInput.InputToolbar.ToolbarOptions's [enterText, hideAddContext, hideImageUpload, hideSelectModel, hideUseCodebase] are judged in gui.src.components.mainInput.InputToolbar, gui.src.components.mainInput.TipTapEditor.TipTapEditor — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
DM9 · Scattered domain decisions· Rule about [assignedTo, createdBy] decided in 2 places · ×1
Rule about [assignedTo, createdBy] decided in 2 places — manual-testing-sandbox.next-edit.next-edit-10-5-sol.Task's [assignedTo, createdBy] are judged in manual-testing-sandbox.next-edit.next-edit-10-5-sol.InMemoryTaskRepository, manual-testing-sandbox.next-edit.next-edit-10-5-sol.TaskAuthorizationService — the same decision, restated. Every copy is a chance to drift, and copies drift silently because each one looks correct on its own. Move the judgement onto the type that owns the members and let the call sites ask it.
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.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 212/224 types (95%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
Logging is not universal — Only 5/13 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `.`, `.`, `binary`, `docs-site` and 3 more.
Nullable reference types not enabled everywhere — 0/1 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.
Skipped (documented): (unnamed test) core/util/isAbortError.vitest.ts:41— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) core/util/isAbortError.vitest.ts:98— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): Need some sample inputs to properly test this core/autocomplete/filtering/streamTransforms/lineStream.vitest.ts:37— Skipped with a documented reason — a deferral, not lazy debt: declared with it.todo — a placeholder that registers a name and runs nothing
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 8 file(s) — `core/llm/openaiTypeConverters.ts`, `extensions/cli/src/services/index.ts`, `extensions/cli/src/ui/components/MemoizedMessage.tsx`, `extensions/cli/src/ui/hooks/useChat.helpers.ts`, `extensions/cli/src/ui/hooks/useChat.imageProcessing.ts`, … (+3 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1796c-1cc1-7297-a0c5-23b49d1c541e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 496 · Warnings: 1377 · Recommendations: 267 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 18:14 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.